From: Mario Limonciello <mario.limonciello@amd.com>
To: Arnaud BERTRAND <arnaud078@gmail.com>,
Alex Deucher <alexdeucher@gmail.com>,
Oz Tiram <oz@shift-computing.de>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/amd/amdgpu: add firmware file fallback for APU VBIOS discovery
Date: Mon, 2 Nov 2026 08:59:40 -0600 [thread overview]
Message-ID: <5d9150eb-eb5e-4788-8945-cfc8084385d4@amd.com> (raw)
In-Reply-To: <CAGxFSwnJYc03fN+XWU8oLW9EbXhmetQuj1s3-m8UdZHoBdGJ8Q@mail.gmail.com>
On 11/1/26 17:31, Arnaud BERTRAND wrote:
> Hi Mario, Alex,
>
> I have two dGPUs : a Radeon RX 6800
> XT and a Radeon RX 6800. They both report the same PCI identity
> 1002:73bf and each has a different VBIOS.
> I hit the same VFCT bus-number mismatch on 7.2.10, but with a different
> outcome: on my machine the device-identity fallback actively breaks the
> second
> dGPU.
> I patched my kernel to remove the fallback, but I would like to have a
> better solution for my use case.
> Would it be possible to apply the patch only to APUs ? That would keep
> Oz's APU case working but a dGPU with a stale bus number would fall
> through to its own ROM, which is the source that is
> guaranteed to match the card in the slot.
> I can provide more details if needed, I am out of my depth here.
> Thanks
> Arnaud
Can you please have a try with this patch series?
https://lore.kernel.org/linux-pci/20261027-vfct-regression-v4-0-0e7190e39c2c@amd.com/
next parent reply other threads:[~2026-11-02 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGxFSwnJYc03fN+XWU8oLW9EbXhmetQuj1s3-m8UdZHoBdGJ8Q@mail.gmail.com>
2026-11-02 14:59 ` Mario Limonciello [this message]
2026-06-26 17:42 [PATCH] " Mario Limonciello
2026-07-05 10:04 ` [PATCH v2] " Oz Tiram
2026-07-05 18:37 ` Mario Limonciello
2026-07-05 19:10 ` Oz Tiram
2026-07-06 0:56 ` Mario Limonciello
2026-07-08 12:36 ` Oz Tiram
2026-07-08 12:55 ` Mario Limonciello
[not found] ` <cc849fb3-224e-43c0-bc50-67fd025009e7@shift-computing.de>
2026-07-08 13:13 ` Mario Limonciello
2026-07-08 16:35 ` Oz Tiram
2026-07-08 16:39 ` Mario Limonciello
2026-07-08 17:53 ` Oz Tiram
[not found] ` <d224d046-0480-4e38-9e93-29a0d37f3331@shift-computing.de>
2026-07-08 17:59 ` Mario Limonciello
2026-07-08 18:02 ` Alex Deucher
2026-07-08 18:03 ` Mario Limonciello
2026-07-08 18:12 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d9150eb-eb5e-4788-8945-cfc8084385d4@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnaud078@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oz@shift-computing.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®