For a distro,just building packages for an architecture is notable support-wise. Those with custom firmware and kernels can pair them with the rocky 10 userspace.

Exactly! The AltArch SIG is exactly where those customization will come from, driven by community support.

Even better title: Rocky will take the RHEL work and rebrand and sell the boards at a discount from China and claim a win and that they're being attacked by IBM.

Man some of y'all really have beef with Rocky...

Because their model is the absolute laziest possible one.

Yes, because the idea of iterate and claim ownership is dishonest and lazy at best.

We've actually been working with Fedora and RH on RISC-V for over a year now :)

Then why does this article give "special thanks" to Fedora, but not Red Hat? Or point out the fact that the vast majority of the Fedora RISC-V porting work is being done by Red Hat employees?

Still, past sins and all that. Not too mention the model and the directions from those at the top.

Great I always applaud contributions and I want to encourage it. But please see the damage done by some quite senior persons on the project and please distance yourselves from them.

I suggest you try and measure yourself using that big stick you're holding up to other people.

As one of the founders of the project, I don't think I'll distance myself from myself.

They could easily support the Pine64 Star64 board as well, the VisionFive2 build of u-boot works on the Star64 too.

Yep, should work fine, just not stepping across the upstream (Fedora) support at the moment.

Even to support one board, they'd need the whole build / testing infrastructure for RISC-V. Likely adding more boards is booing to be easy now, and any architecture-specific regressions, easier to spot and fix timely.

For sure, we needed a build infrastructure for RISC-V. I started out with five VisionFive 2's in my lab, and they're still doing work as needed. Granted, those are quite slow and painful because some builds will take a long, long time on those (for example, GCC took 7 days at the beginning, but we have it at about 5 days plus change now). Ever since we've added SiFive P550's to the mix, it has made it much faster for us to identify build issues and get them rectified. I still happen to use my VF2's for the "tiny" builds.

It's true that since we've had a usable build root since last 2024, it gives our AltArch group the opportunity to build different kernels to support other SBC's or boards like they already do for ARM SBC's (rasperry pi for example, since that support isn't native to the EL kernel). So while we support the VF2's and QEMU out of the box, that group will handle the additional kernels for more hardware support.

I'm actually looking forward to seeing what other boards the AltArch group will happen to add support for.