News for hackers. Stuff that matters.
Re:I have come to bury the BIOS, not to open it: The need fo... by zokier on Sunday October 09, 2022 @06:18PM (#33145840)
Its kinda difficult to understand what are the key differences between their approach and what coreboot does with Linux payload, which afaik does not use any BIOS/UEFI layer in between and also is pretty minimal on coreboot size => boot as early as possible to Linux
Re:I have come to bury the BIOS, not to open it: The need fo... by mlindner on Sunday October 09, 2022 @06:30PM (#33145941)
Someone from Oxide (maybe Bryan) talked a bunch about how the philosophy of Oxide differs from Coreboot somewhere. I remember either reading about it or hearing it, but I can't for the life of me remember where I heard/read it.
Re:I have come to bury the BIOS, not to open it: The need fo... by panick21_ on Monday October 10, 2022 @05:18AM (#33149378)
The difference is that coreboot comes up and runs a payload, something like LinuxBoot. LinuxBoot is then responsible to find the actual OS that you want to boot, and uses kexec to boot that OS. LinuxBoot still has to pass hardware information to the HostOS and then hand over control.

In Oxide this doesn't happen, the Pico thingy boots into their OS and that's it. There is no in-between step. The OS then simple loads the additional things it needs. It never hands of control to anther kernel.

At least this is how I understand it.

Re:I have come to bury the BIOS, not to open it: The need fo... by zokier on Monday October 10, 2022 @11:35AM (#33152727)
> LinuxBoot is then responsible to find the actual OS that you want to boot, and uses kexec to boot that OS

I'm not super familiar with coreboot, but isn't that step kinda optional? I mean could you start booting up userland directly too?

Re:I have come to bury the BIOS, not to open it: The need fo... by panick21_ on Monday October 10, 2022 @05:49PM (#33156785)
I have not heard of anybody doing this so I would assume there is some reason for that.
Re:I have come to bury the BIOS, not to open it: The need fo... by sounds on Monday October 10, 2022 @07:31PM (#33157607)
I see the sibling comment, so here's my two cents -

I wonder if there's some confusion because LinuxBoot is being talked about relative to Oxide. LinuxBoot isn't trying to do that.

It was originally a project called "LinuxBIOS" at Los Alamos National Labs to get their supercomputer to boot up in a reasonable amount of time. Once the team started down the path of "rip out the legacy BIOS" they discovered that a lot of things become simpler.

LinuxBoot was written with the goal of booting up the machine to GRUB, like this:

(CPU Reset) > LinuxBoot > GRUB > Linux

See the description of this video (though the video is worth the watch): https://vimeo.com/724454408 "Why Linux? Because firmware always evolves to become an operating system. Rather than wait for evolution to take its course, LANL decided to save some time and use Linux as the BIOS: hence LinuxBIOS."

See also https://lwn.net/Articles/10590/

-----

And the answer to your question: "could you start booting up userland directly?" I think if the LinuxBoot authors were around they would mention something about how constrained the on-board flash chip is (SPI Flash). There's room for LinuxBoot and maybe GRUB, but there is not room for all the drivers needed to get to userland.

Re:I have come to bury the BIOS, not to open it: The need fo... by panick21_ on Monday October 10, 2022 @08:39PM (#33158107)
The current normal is:

(CPU Reset) > Coreboot > LinuxBoot > GRUB (or whatever) > Linux

Coreboot: https://www.coreboot.org/

LinuxBoot: https://www.linuxboot.org/

LinuxBIOS was renamed Coreboot for marketing reasons.

LinuxBoot is much newer concept.