4 comments

[ 1.8 ms ] story [ 18.3 ms ] thread
It's tragic to see these hardware vendors repeat mistakes of the past by forcing UEFI on platforms that do not need it.
It's the opposite. It's tragic to have no baseline when there's an accepted very good platform that basically works that everyone else uses. It's tragic to go it alone.
Server platforms definitely need UEFI or something very much like it. How else can a server boot from eg. a network card that's not directly supported by the firmware? You need something like UEFI to define a standard for option ROMs, and that standard needs a stable, backward-compatible ABI.

AFAIK, only UEFI and ACPI fulfill that requirement currently (ok, there's Open Firmware, but that's quite esoteric) - eg. Coreboot doesn't really work well in this situation: multiple vendors, different update lifecycles and possibly closed-source binaries.

The first server board to implement this spec will instantly become the best desktop board for RISC-V. Simply because it'll follow a standard.