From: Alex Deucher <alexdeucher@gmail.com>
To: Arnaud BERTRAND <arnaud078@gmail.com>
Cc: Oz Tiram <oz@shift-computing.de>,
airlied@gmail.com, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
simona@ffwll.ch
Subject: Re: [PATCH] drm/amd/amdgpu: add firmware file fallback for APU VBIOS discovery
Date: Mon, 2 Nov 2026 08:58:31 -0500 [thread overview]
Message-ID: <CADnq5_PyctWJK2k4-CutYFNPkuMprmZE98d2JjodBQkTLGJhDA@mail.gmail.com> (raw)
In-Reply-To: <CAGxFSwnBDM93ouN6Aq2ppm5zF1h19XE6NJ92NT2UEhMP1P4xEg@mail.gmail.com>
On Mon, Nov 2, 2026 at 3:07 AM Arnaud BERTRAND <arnaud078@gmail.com> wrote:
>
> Hello,
>
> 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.
Should be fixed with this patch series:
https://patchwork.freedesktop.org/series/176969/
Alex
> Thanks
> Arnaud
next prev parent reply other threads:[~2026-11-02 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:37 Arnaud BERTRAND
2026-11-02 13:58 ` Alex Deucher [this message]
2026-11-03 20:59 ` Arnaud BERTRAND
-- strict thread matches above, loose matches on Subject: below --
2026-06-21 17:32 Oz Tiram
2026-06-21 18:01 ` Oz Tiram
2026-06-26 17:42 ` Mario Limonciello
2026-06-26 19:38 ` Alex Deucher
2026-07-05 10:15 ` Oz Tiram
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=CADnq5_PyctWJK2k4-CutYFNPkuMprmZE98d2JjodBQkTLGJhDA@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnaud078@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oz@shift-computing.de \
--cc=simona@ffwll.ch \
/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®