Index | Thread | Search

From:
Ted Bullock <tbullock@comlore.com>
Subject:
Re: radeondrm: use the common KMS console path on sparc64
To:
Janne Johansson <icepic.dz@gmail.com>
Cc:
tech@openbsd.org
Date:
Tue, 6 Oct 2026 09:48:42 -0600

Download raw body.

Thread
On Tue, Oct 6, 2026 at 8:43 AM Janne Johansson <icepic.dz@gmail.com> wrote:
>> > This feels like it should be guarded by an ifdef based on if the platform is big endian or not, and not just sparc64.
>>
>> Hi Janne,
>>
>> I checked this. Radeon already configures the framebuffer byte order
>> handling for big endian. The additional difference on sparc64 is that
>> it uses little endian pages for PCI framebuffer access. Mac and PowerPC
>> don't do that. SPARC has its own approach to handling PCI.
>> So I think this needs to stay sparc64, since the other platforms aren't
>> affected by this change, to my knowledge.
>
>
> I'll take your word for it, it's probably still better than not having that patch, and
> the amount of other bigendian XVR100 users might be zero, so..
>

Well,

Sort of, it was a common enough card in its time, I think it was the
radeon 7000 when sold as a pc device

The exact chip is in a ton of old power pc mac stuff as well so it's
reasonable to still pay attention.

In this case sun actually just rebadged a mac pci card when they made
this sparc workstation. When I pay attention to the sparc and power pc
list and bugs relating to openbsd I regularly see the telltale
firmware loading defect too with this card. So, all that being said,
it's worth fixing, admittedly it's like 20 years late to make any
difference to like 99.972% of users.

Anyway I have some screen captures to show the difference and a couple
more small patches too after this one.

-- 
Ted Bullock <tbullock@comlore.com>