Anonymous user
BOOTBOOT: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
| [unchecked revision] | [unchecked revision] |
m (→Console) |
mNo edit summary |
||
Line 18:
* CDROM, El Torito UEFI boot Extension (x86_64)
* ISOLINUX / LILO / BOOTLIN / etc. (x86_64 via the Linux kernel boot protocol)
* COREBOOT: as a primary payload in ROM (x86_64)
For GRUB compatibility, BOOTBOOT is also Multiboot compliant, so you can add it to the grub.cfg in it's own entry. This is useful if want to dual boot multiple OSes.
Line 27 ⟶ 28:
If despite the warning you decide to [[Roll Your Own Filesystem]], then BOOTBOOT is definitely for you. You can either write an FS module (one function), or just make sure the kernel is the first executable in the archive / on the partition. BOOTBOOT is capable of loading kernels from unknown file systems as well.
Optionally you can load your OS from ROM (see qemu's -option-rom command line argument, or bochs rc file; or with [https://coreboot.org coreboot] as a BIOS using qemu -bios), and the Raspberry Pi version can also load the ramdisk over serial line. Although it's not implemented as of yet, the BOOTBOOT protocol allows loading the initrd from a TFTP server.
== Your Kernel ==
| |||