cross-posted from: https://lemmy.ml/post/46604530
Built for Rapid Upstream Delivery
Rolling releases with upstream tracking bring new RISC-V features and fixes to you sooner—less waiting, less rework.
Built for RISC-V Developers
Stay close to upstream to reduce backports and forks. Easier reproduction, faster debugging, smoother upstream contributions.
Built for Early Validation
Surfaces firmware, platform semantics, and Linux interoperability issues early—so vendors fix faster, reduce divergence, and reach mainstream OS compatibility sooner.
Risc-V is very exciting. The future of open computing.
Does risc-v have uefi like x86 or it requires specific image for every machine like before?
There is a UEFI Requirements section in the RISC-V Boot and Runtime Services Specification (BRS) specification. But this is optional and as far as I know most SBCs don’t use it. So yeah because of poor mainline Linux kernel and other components (like SBI) upstreaming by RISC-V systemproviders it is still a sad case that often you need a system specific image. So yeah I think we will need to wait until RISC-V breaks more into PC-like and server space before BRS and similar specs get used more.
I don’t think it will happen anyway, considering ARM still doesn’t do it and we have apple M chips and snapdragon ARM laptops.
But let’s hope I’m wrong
Yes, both.
The architecture is really varied. You can get super cheap SoCs that are barely capable of running FreeRTOS, and you can get 100+ core beasts with EFI, PCIe, etc.