Difference between revisions of "Payloads"

From coreboot
Jump to: navigation, search
(Possible Payloads)
m
Line 35: Line 35:
 
* [http://www.gnu.org/software/gnufi/ GNUFI] (UEFI)
 
* [http://www.gnu.org/software/gnufi/ GNUFI] (UEFI)
 
* [[Etherboot]] — Includes FILO, and its FILO supports SATA and USB booting.
 
* [[Etherboot]] — Includes FILO, and its FILO supports SATA and USB booting.
* [[ADLO]] — Glue layer to 16-bit Bochs BIOS. Allows booting [http://en.wikipedia.org/wiki/Windows_2000 Windows 2000] and [http://openbsd.org/ OpenBSD].
+
* [[ADLO]] — Glue layer to 16-bit Bochs BIOS. Allows [[Booting Windows using LinuxBIOS|booting Windows]] and [http://openbsd.org/ OpenBSD].
 
* [[Plan 9]] — A distributed operating system.
 
* [[Plan 9]] — A distributed operating system.
 
* [[memtest86]] — Can stress-test your RAM.
 
* [[memtest86]] — Can stress-test your RAM.
 
* [[RedBoot]] / [[eCos]] — Real-time OS for embedded systems; initial port to ELF completed but no longer available.
 
* [[RedBoot]] / [[eCos]] — Real-time OS for embedded systems; initial port to ELF completed but no longer available.

Revision as of 11:08, 8 September 2007

LinuxBIOS in itself is "only" minimal code for initializing a mainboard with peripherals just enough for a Linux kernel to take over and do the rest. LinuxBIOS does not contain a kernel per se.

After the initialization, LinuxBIOS jumps to a payload and while there has been discussion about stacking payloads that's currently not in practice.

The payload was originally intended to be a Linux kernel stored in flash. Flash ROM growth rate was anticipated optimistically however, today there are not many mainboards that actually have enough flash ROM room for a kernel. 512KB can be seen here-and-there and a few boards come with 1MB. Recent kernels really want that MB, and then you'll only have room for 300-400 KB of initial ramdisk, which could be too small too, depending on the application. During testing, a payload may also be downloaded via X-Modem from the serial debug console, saving flashing time.

So, other payloads are used; the two major ones are FILO and Etherboot. FILO loads a kernel from a filesystem on an IDE device and Etherboot loads a kernel from the network or from a filesystem on an IDE device.

If you're using FILO there is no Linux kernel until FILO loads it, and the kernel loaded by FILO (or Etherboot) can absolutely be the one you want to run in your system. Just set it up with the correct root and init commandline so that it can start init.

Possible Payloads

  • Linux — Boot into a Linux kernel directly.
  • FILO — Simple bootloader with filesystem support.
  • GRUB2 — Will replace FILO. Does not work, yet.
  • Mitch Bradley's Open Firmware — IEEE1275-1994 Open Firmware
  • CodeGen's SmartFirmware — IEEE1275-1994 Open Firmware
  • OpenBIOS — IEEE1275-1994 Open Firmware
  • GNUFI (UEFI)
  • Etherboot — Includes FILO, and its FILO supports SATA and USB booting.
  • ADLO — Glue layer to 16-bit Bochs BIOS. Allows booting Windows and OpenBSD.
  • Plan 9 — A distributed operating system.
  • memtest86 — Can stress-test your RAM.
  • RedBoot / eCos — Real-time OS for embedded systems; initial port to ELF completed but no longer available.