3 ms·
>It's kind of an issue for ARM too but they're a bit further towards solving it than RISC-V. Can you elaborate on why you think so? I understand it is the opp
by snvzz 3y ago
>It's kind of an issue for ARM too but they're a bit further towards solving it than RISC-V.
Can you elaborate on why you think so?
I understand it is the opposite: RISC-V is much further towards solving it.
This is because RISC-V has put effort from the start into standardizing boot process (spl -> sbi -> uboot|uefi), ISA (profiles), the firmware-kernel interface (sbi, uefi protocol, acpi) as well as the platform itself (platform spec, standards for interrupts, timers, hypervisor support, the uart requirement, the watchdog and further platform standardization efforts).
This has happened (and is happening still) before significant deployment of SoCs using RISC-V microarchitectures as the application processor.
Meanwhile, ARM realized, quite late, that this is important, and is lagging behind, with plenty of non-fixable, bespoke platform hardware deployed, and low vendor uptake as they are asking their clients to change what they already have in place.
- ryukafalz 3y agoI haven't been keeping up to date with RISC-V happenings lately but does this imply that it'll be easier for distros to have live images that can install to arbitrary RISC-V machines like we're used to on x86? If so, that's exciting!
- snvzz 3y ago>it'll be easier for distros to have live images that can install to arbitrary RISC-V machines like we're used to on x86? Yes. The experience will be equal or better over the IBM PC-derived platform, by design. PC was an accidental platform, RISC-V platform spec is an intentional (and very informed) one.