From: "Christian König" <christian.koenig@amd.com>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: allocate dummy_page without DMA32 on fail
Date: Fri, 17 Jul 2026 09:37:23 +0200 [thread overview]
Message-ID: <679e18a5-9402-41dc-bd7d-58bc7714ff62@amd.com> (raw)
In-Reply-To: <CAEev2e8e4Q2zgQxkodBzNpXCDCFhE4femijQ_K8yQrKe7bXn=Q@mail.gmail.com>
On 7/16/26 16:31, Anirudh Srinivasan wrote:
...
>>>>
>>>> What could be possible is to add a special quirk for your platform to not allocate the dummy page as DMA32 in the first place.
>>>
>>> So some kind of a whitelisted set of PCIE vendor/ID combos (with
>>> working IOMMUS?) where we fallback to non DMA32 ranges?
>>
>> No, what you are testing here is basically that display is functional and not anything else.
>
> I think I understand this now. You're suggesting that we skip
> allocating the dummy page in this specific case.
Well that won't really work.
We had some minimal fallback to enable only CRTCs in the radeon driver but that was more or less only used to print error messages and not let people end up with a completely black desktop if HW initialization fails.
As far as I can see you can't use the driver/HW combination on this platform when DMA32 isn't available.
You could give efifb or vesafb a try, that is pretty much the same functionality as radeon without acceleration.
On the other hand what HW generation do you have? Maybe it's possible that this is something newer like SI or CIK? In that case you could try the more modern amdgpu driver, it should be able to better deal with the situation.
Regards,
Christian.
>
>>
>> Regards,
>> Christian.
>>
>>>
>>> Regards
>>> Anirudh Srinivasan
>>
prev parent reply other threads:[~2026-07-17 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 16:03 Anirudh Srinivasan
2026-07-15 9:15 ` Christian König
2026-07-16 2:08 ` Anirudh Srinivasan
2026-07-16 7:34 ` Christian König
2026-07-16 14:31 ` Anirudh Srinivasan
2026-07-17 7:37 ` Christian König [this message]
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=679e18a5-9402-41dc-bd7d-58bc7714ff62@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome