RISC-V Server Platform Spec Ratified(github.com)
github.com
RISC-V Server Platform Spec Ratified
https://github.com/riscv-non-isa/riscv-server-platform/releases/tag/v1.0
9 comments
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.
It's tragic to see these hardware vendors repeat mistakes of the past by forcing UEFI on platforms that do not need it.
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.
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.
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.
Well, implementations of UEFI are all over the board because vendors have their own ideas, that leads to compatibility issues.
It is also a security risk, as it is essentially a huge system (compared to BIOS) under the actual OS, compromise the former and own the latter. The larger code base, the larger attack vector.
Coming back to UEFI implementations, how many of them are actually open source and do not have un-vetted code running (again under your OS)?
Yes, UEFI do have some positives but the security risk far outweighs them.
It is also a security risk, as it is essentially a huge system (compared to BIOS) under the actual OS, compromise the former and own the latter. The larger code base, the larger attack vector.
Coming back to UEFI implementations, how many of them are actually open source and do not have un-vetted code running (again under your OS)?
Yes, UEFI do have some positives but the security risk far outweighs them.
It is increasingly rare for EDK2 (A modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications from www.uefi.org: https://github.com/tianocore/edk2) to not be used as the basis for a secure boot load plus runtime firmware services stack).
Vendor veerage from vanilla upstream edk2 does occur of course but it does so also with legacy BIOS’. There’s no getting around it in the real world with very very few exceptions.
UEFI evolved to solve standardized boot and firmware at scale and the internet as it stands today would struggle without a standard like it. RISC-V taking a different approach would be swimming against the tide backwards to irrelevance.
Vendor veerage from vanilla upstream edk2 does occur of course but it does so also with legacy BIOS’. There’s no getting around it in the real world with very very few exceptions.
UEFI evolved to solve standardized boot and firmware at scale and the internet as it stands today would struggle without a standard like it. RISC-V taking a different approach would be swimming against the tide backwards to irrelevance.
The only thing I can imagine that's worse than having weird vendor implementations of a standard that cause unexpected chaos is not having a standard to have any expectations in the first place, to have everyone doing whatever.
The security benefits of having something that has a robust capable platform with a good test suites feels unmatched compared. Even if you don't know the code (and most are just edk2), at least there's a pretty well defined surface, whose expectations we can test.
I'm open in principle to the idea that maybe UEFI isn't the right fit, that there's other things we should try. but if that answer is BIOS, i'm going to laugh my way out of this thread. Maybe not strictly required but man, the wild incredible janky world of weird antics required to get PXE or a add-on drive card running under bios: it was a piecemeal bodge through and through. I don't know what we see we even try to consider?
The security benefits of having something that has a robust capable platform with a good test suites feels unmatched compared. Even if you don't know the code (and most are just edk2), at least there's a pretty well defined surface, whose expectations we can test.
I'm open in principle to the idea that maybe UEFI isn't the right fit, that there's other things we should try. but if that answer is BIOS, i'm going to laugh my way out of this thread. Maybe not strictly required but man, the wild incredible janky world of weird antics required to get PXE or a add-on drive card running under bios: it was a piecemeal bodge through and through. I don't know what we see we even try to consider?
Hear! Hear!!
>Well, implementations of UEFI are all over the board because vendors have their own ideas, that leads to compatibility issues.
RISC-V has specifications on how UEFI should be implemented.
It's not just "use UEFI".
RISC-V has specifications on how UEFI should be implemented.
It's not just "use UEFI".