If x86 dies we will wind up with a bunch of devices where step 1 is "run this code to exploit a buffer overflow to bypass the locked bootloader. Only works on v1.2 PCB revision 7"
? Chromebooks are like one of two decent non-PC options (the other is Macs). AFAIK every Chromebook can be flipped to developer mode in <5min and then you can boot anything you want.
And the aftermarket UEFI is a great thing - it means that Chromebooks are probably the easiest+cheapest way to have a coreboot machine - but you don't actually need that; the default firmware will, in developer mode, boot any properly-formed image, which is a touch annoying but does in fact let you boot any OS that handles that boot system without replacing the firmware. One of my main machines right now is an ARM chromebook that runs postmarketos on the stock firmware.
Arm ecosystem is cleaner in my experience and learned from the mistakes of the past. Arm CPUs are still not as fast as high-end x86 chips, but it's just a matter of time before that market is also eaten by Arm.
[1] https://community.arm.com/oss-platforms/w/docs/525/device-tr...
Meantime, companies such as PowerVR or ARM are funding their own open source mesa3d drivers.
DTB only describes what blocks are present, if the kernel doesn't know what "crapvendor,lockinregulator" means it would not work. Vs ACPI that actually provides drivers, however crappy.
PS2 and MCA architecture was a kind of attempt to recover control over the PC, but it was too late.
This was a fundamental misunderstanding by IBM. The PC exploded, not because it was from IBM, but because it was not locked down. IBM wanted to re-create their locked-down world; the market was never going to go where IBM wanted it to.
Note that neither RISC-V nor aarch64 are any worse in that regard.
If anything, they're doing much better platform standardization wise.
As far as I am aware, it does not exist.
They were quite late with everything platform related, and suffer from it.
I think x86(-64) is complete trash, and it would be nice to have something better, but we're not going to get there if "x exists" is a stand-in for "x is promoted and encouraged".
ARM is a handful of totally incompatible SoCs and you are totally dependent on SoC integrator providing support (hopefully in the form of throw-over-the-fence-and-forget Linux kernel headers, but more common are just kernel binaries) to run it at all. In theory UEFI supports ARM, but can I buy a desktop ARM processor that does? And this is going to be worse with RISC-V because hardware vendor are not interested in providing platform compatibility. So we would be back in pre-PC era platform-wise.
There is no replacement for x86, not because it is impossible to replace, but because no vendor is interested in making one.