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.
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.
@lemmy.ml
RISC-V (pronounced "risk-five") is a license-free, modular, extensible instruction set architecture (ISA).
riscv.org
go to feed...
@lemmy.ml
RISC-V (pronounced "risk-five") is a license-free, modular, extensible instruction set architecture (ISA).
riscv.org
go to feed...
Does risc-v have uefi like x86 or it requires specific image for every machine like before?
save