> ELFv2 BE ABI works fine on ppc64.

Yes, I know. Void PPC successfully started it some years back, as comment #50 has been a testimony to.

> I've been using it since v6.2 and never had any problems with it. Kernel also
> gets a little bit smaller. As of v6.3 you can also build your BE kernel with
> clang/lld (at least clang-15 is needed), which was not possible before.

Yes, I took as much from your comment #70 and added the Clang info shortly after to comment #69 :-)

> AFAIK it's only a ppc64-thing. 32bit ppc uses a different ABI anyhow.

Yes both ELFv1 and ELFv2 ABI are PPC64-only (see comment #65). And yes, Linux/PPC32 uses SVR4 ABI (see comment #67).

:-D Your memory of my postings is certainly better than mine.

So the news value really only would be ELFv2 BE ABI going default for v6.5. Which is what you already posted.

Update:

> first experimental Live ISO image of [...] Chimera Linux [...] for PPC64BE

PPC64BE now regular release architecture: https://repo.chimera-linux.org/live/latest/

PPC32 now regular release architecture as well:
https://chimera-linux.org/news/2025/02/new-images.html
https://repo.chimera-linux.org/live/latest/


Edit: added info about PPC32 release

[ Edited by Andreas_Wolf 17.02.2025 - 13:22 ]

Ok, then I'll try the new ISO. The beta one from July did not boot on my G5...

Addendum:

>> ELFv2 BE ABI works fine on ppc64.

> Yes, I know.

This topic (ELFv2 BE ABI on VSX-less PPC64) under debate again, this time in BSD context instead of Linux:

https://lists.freebsd.org/archives/freebsd-arch/2025-December/001145.html
https://lists.freebsd.org/archives/freebsd-arch/2025-December/001146.html

Update:

> PPC64BE now regular release architecture: [...]
> PPC32 now regular release architecture as well: [...]

"we are planning to retire support for the big-endian 32-bit PowerPC and 64-bit POWER platforms."
https://chimera-linux.org/news/2026/03/retiring-powerpc.html

Quote:That is unfortunate, but was to be expected and for understandable reasons.

And more or less the same outcome as for q66 previous project, Void Linux PPC.

I think the reasons he cites are valid, but at least on mainline mesa the situation hopefully will improve, at least for the r300 driver as a very capable dev is willing to spend time on fixing BE issues (klick).