I'd be curious why because the PC model seems to be way more user-friendly, competition-friendly, and long-term-reliable than the current ARM model. I wish I could just download an ISO of Android 13 and install it on almost any Android phone like I could Windows.
Open Firmware—between the device tree system and the bytecode driver system—plus ELF provide a truly universal boot protocol for 32-bit and larger systems. And not only that, major and tractable implementations are now Open Source too, including things like the bytecode compilers.
It’s practically unconscionable that modern ARM and RISC-V don’t simply require Open Firmware boot support.
All the pieces are in place for RISC-V to effectively dodge boot chaos. Way before the server/workstation RISC-V hardware hit the market.
In ARM, it's a mess. Because ARM took way too long to do way too little re: boot standardization.
Imagine scaling that up to GPUs! The device needs to describe itself because IT is unique.
I encourage you to spend more time with it. Meet your hero. Get to know it. Understanding will surely follow. 8)
That "describes itself to the OS" part is actually often being done by a complete OS as well.
> Unfortunately, UEFI/ACPI or simliar seems to be going nowhere in the ARM world, so it doesn't seem installing Windows/Linux is going to be as easy on ARM as on x86 anytime soon.
That's a really good thing. Bryan rants about ARM trying to go that way and thinks it's a terrible idea. I'm glad it's failing, assuming that's actually the case.