The boot process and various devices
I'm writing from a limited perspective, so constructive criticism appreciated. In this thread, I'm recording some thoughts about how the OS gets from files into the memory of various boards, and what might make this more unified and easier and/or more flexible.
Current U-boot
My knowledge comes from the mvebu64 and rockchip64 families. At this time, the board boot process starts from code in the processor that attempts to find u-boot, and u-boot runs a script from its environment that
How? This isn't a kernel configuration option, so what is doing so afterward? And then how are you telling uboot to decompress it, that's not in your extlinux config?
https://www.kernel.org/doc/Documentation/arm64/booting.txt
"The AArch64 kernel does not currently provide a decompressor and therefore requires decompression (gzip etc.) to be performed by the boot loader if a compressed Image target (e.g. Image.gz) is used. For bootloaders that do not implement this requirement,