book
book copied to clipboard
LinuxBoot book which contains the documentation in markdown format
You may end up in limbo. https://eastrivervillage.com/kexec-tools-with-the-hidden-purgatory/
https://github.com/mullvad/system-transparency > stboot is System Transparency Project’s official bootloader. It is a [LinuxBoot](https://www.linuxboot.org/) distribution based on [u-root](https://github.com/u-root/u-root). The source code of stboot can be found at https://github.com/system-transparency/stboot.
https://wiki.odroid.com/odroid-n2/software/boot_sequence#boot_from_spi
First code is often: `arch/$ARCH/kernel/head.S` ## x86 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/machine_kexec_64.c?h=v6.15-rc6#n53 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/x86_init.c?h=v6.15-rc6#n123 ## arm has no `kexec_file_load` yet, WIP was there https://lore.kernel.org/linux-arm-kernel/[email protected]/ ## arm64 tbd ## riscv tbd
a loader is just a program that - parses config/binary formats - loads data to memory - uses kexec and reboot syscalls u-root already has lots of parsers, and different...
What tools are there? - https://github.com/systemd/mkosi - https://github.com/xdbob/sbtools
https://youtu.be/GTE8vdIEATs?si=6eOn_FNngoLZxGs-&t=882
Roughly, regardless of EFI or DT, register conventions are used to pass information to the OS. The respective register would hold a memory address, and that would point to either...
The [Device Tree spec](https://devicetree.org) is quite freeform, not requiring much in terms of naming of nodes and properties, or what properties to have, but very few. However, Linux is where...
Some history is to be found in older discussions - https://news.ycombinator.com/item?id=15579592 - https://news.ycombinator.com/item?id=15748900 - https://news.ycombinator.com/item?id=16259373