4 ms·
Not a word about uefi or any other kind of standardized booting. Not surprising given the use case list but still disappointing.
by baq 3y ago
Not a word about uefi or any other kind of standardized booting. Not surprising given the use case list but still disappointing.
- camel-cdr 3y agoNo idea why they would talk about that in such a blog post, but as I understand it, the booting process will be standardized by the platform specification [0]. [0] https://github.com/riscv/riscv-platform-specs/blob/main/riscv-platform-spec.adoc https://github.com/riscv/riscv-platform-specs/blob/main/risc...
- xvilka 3y agoUEFI is a bad choice for embedded. It has too much of the PC quirks, which is mostly irrelevant on ARM or RISC-V. They should have tried to create something new, without x86 cruft.
- pgeorgi 3y agoARM: "This document defines the Boot and Runtime Services expected by an enterprise platform Operating System or hypervisor, for an SBSA-compliant Arm AArch64 server which follows the UEFI and ACPI specifications." (https://documentation-service.arm.com/static/5fb7e415d77dd807b9a80c80?token= https://documentation-service.arm.com/static/5fb7e415d77dd80...) Also "This document identifies the Arm and industry standard firmware interfaces applicable to the Arm 64-bit architecture. They include the PSCI, SMCCC, UEFI, ACPI, SMBIOS, and DT interfaces. Requirements that are based on these interfaces are specified. In addition, various recipes are created to accommodate the various operating systems and hypervisors." (https://documentation-service.arm.com/static/627a75d3148af93a314a2b36?token= https://documentation-service.arm.com/static/627a75d3148af93...) Two out of three "recipes" are UEFI-based. -- As for RISCV, they're embracing UEFI, too: https://riscv.org/announcements/2022/06/risc-v-announces-first-new-specifications-of-2022-adding-to-16-ratified-in-2021-risc-v-international/ https://riscv.org/announcements/2022/06/risc-v-announces-fir... Note that the announcement also refers to SBI, which is RISCV's poor-man's implementation of x86 SMM, quickly becoming a required component on the platform because OSes call into that.
- rwmj 3y agoOpenSBI is open source so hardly comparable to SMM. https://github.com/riscv-software-src/opensbi https://github.com/riscv-software-src/opensbi
- pgeorgi 3y agoThere's Open Source SMM as well (e.g. https://review.coreboot.org/plugins/gitiles/coreboot/+/HEAD/src/cpu/x86/smm/smm_module_handler.c https://review.coreboot.org/plugins/gitiles/coreboot/+/HEAD/...) and it's still a pain. "There's services outside the kernel's control that may or may not do what the kernel/userland/user expect because they can be independently updated, and, oh by the way, they're really powerful" is simply a pain to deal with.
- snvzz 3y ago>SBI, which is RISCV's poor-man's implementation of x86 SMM, SMM is totally opaque and does whatever it wants, kidnapping the cpu and giving it back after a random amount of time if at all. Fuck determinism or meeting any sort of hard realtime requirements. It hides bugs and architecture details from the OS, and it often can't even be disabled. SBI serves a similar role, without the opacity. OS can make requests to it through APIs that are part of the spec, and even take over all its roles. It has been co-designed by hardware and software (operating systems and embedded) people across the industry, both companies and independent members. It's not even comparable. Go read the SBI 1.0 spec, and the SBI 2.0 draft.
- pgeorgi 3y agoThis is a thread about Qualcomm looking into RISC-V. Seeing how "great" their ARM-based designs are, they will manage to make a real mess out of SBI soon enough and there will be weeping and gnashing of teeth. I'll stock up on my popcorn supplies, this will be fun to watch from a distance.
- snvzz 3y agoNevermind about making a non-compliant SBI implementation. Why make an implementation in the first place? There's no reason to use anything else than opensbi.
- crote 3y agoUefi is pretty pointless when your device doesn't even run a full-blown operating system. In the embedded world your software knows exactly what hardware it is going to run on, so uefi is just a waste of time. You only need something like uefi when you start using mostly hardware-independent software, like trying to run Linux on it. A lot of the chips these companies make are not even remotely close to that.
- treyd 3y agoMany of these devices will run Linux though, and it's becomming increasingly more common as even the low end chips are pretty capable nowadays. It could be worthwhile to build some lightweight alternative to UEFI that just handles disk identification and handing off a devtree to whatever bootloader comes after it instead of implementing the behemoth of a spec that is all of UEFI. Call it "LWFI", "light-weight firmware interface"?
- monocasa 3y agoThat just sounds like uboot.
- CameronNemo 3y agoUboot does efi. It can also just exec Linux directly. But more interesting is whether the ram training code and ring -1 layers are open source.
- crote 3y agoNot really, no. Linux isn't going to run on a chip with 48k of memory which doesn't even have an MMU, and doing disk identification is pretty pointless when your "disk" is 256k on on-chip flash - or a hardsoldered 2M SPI chip if you are really lucky.
- constantcrying 3y agoThis is an announcememt of a partnership, why would they talk about some technical details?