Red Hat announced RISC-V yesterday with RHEL 10. So this seems rather expected.<p><a href="https://www.redhat.com/en/blog/red-hat-partners-with-sifive-for-risc-v-developer-preview-for-red-hat-enterprise-linux-10" rel="nofollow">https://www.redhat.com/en/blog/red-hat-partners-with-sifive-...</a>
I understand why people use RH and Rocky and even Oracle: the rpm wranglers. However its not for me.<p>My earliest mainstream distro was RH when they did it just for fun (pre IBM) and then I slid slightly sideways towards Mandrake. I started off with Yggdrassil.<p>I have to do jobs involving RH and co and its just a bit of a pain dealing with elderly stuff. Tomcat ... OK you can have one from 1863. There is a really good security back port effort but why on earth start off with a kernel that is using a walking stick.<p>Perhaps I am being unkind but for me the RH efforts are (probably) very stable and a bit old.<p>It's not the distro itself either. The users seem to have snags with updating it.<p>I (very generally) find that RH shops are the worst at [redacted]
Maybe a dumb question but how do non x86 boards normally boot Linux images in a generic way? When I was in the embedded space, our boards all relied on very specific device tree blobs. Is the same strategy used for these or does it use ACPI or something?
How do they get access to the source code? I read some time ago that RH has changed how they provided the source code and that it was (almost) impossible to get it now?
I cannot wait for those ultra-performant rv64 micro-architecture manufactured with the latest silicon process. One less toxic PI lock and much cleaner assembly.