Redox OS (the Unix-like microkernel OS written in Rust) is working on a native Coreboot payload along with bug fixes and a new release.
Lead Redox OS developer Jeremy Soller tweeted that "it's time for Redox OS to become a Coreboot payload." It looks like Redox OS is working on native Coreboot payload support for this interesting Rust operating system rather than first needing to use one of the bootloaders as a Coreboot payload before hitting Redox OS.
[...] The Redox OS twitter also went on to outline they are working on fixes to their networking stack, fixes to curl / cargo / git, advancing towards the state of being able to self-host itself (build Redox OS on Redox OS), improving the relibc C library implementation, porting more applications to running on Redox OS, and at that point to also prepare a new release. And, yes, exploring Coreboot payload capabilities.
Previously: Microkernel, Rust-Programmed Redox OS's Devs Slam Linux, Unix, GPL
(Score: 2, Informative) by Anonymous Coward on Monday February 25 2019, @07:21AM
Coreboot is at the lowest level. It loads from the bootblock, finds itself in the ROM, initializes the RAM, and then executes the firmware payload, i.e. the BIOS/UEFI level. It can be set to fire off all sorts of payloads, and it is the payloads responsibility to finish setting up the hardware and then running the next step of the boot process (such as checking the MBR, in the case of a BIOS payload, like SeaBIOS). The most common payload is probably SeaBIOS, but there are UEFI and Open Firmware payloads too. There are also stacked payloads, like the GNU GRUB or iPXE payloads, which are actually those bootloaders booted directly from RAM by the true payload, rather than following the rest of the normal boot process used to normally launch them.