A couple of improvements for the RPI4b target #461
Conversation
We now mount the /boot partition. By that, we also avoid config drift, as previously changes to files on /boot were not effective, as the bootloader only looks at the first partition, but not the boot dir in the rootfs. Signed-off-by: Felix Moessbauer <[email protected]>
We currently only support imaging with wic. By that, limit the IMAGE_INSTALL to that mode as well. This speeds avoids building these dependencies when just creating a rootfs. Signed-off-by: Felix Moessbauer <[email protected]>
This brings us support for Linux 6.12 kernels and is still compatible with the 6.1 kernel from bookworm. It also carries bugfixes. Signed-off-by: Felix Moessbauer <[email protected]>
|
If we switch to the raspian kernel, we would have the information but other issues. I prefer to update to a 6.12 kernel later on and then continue the work on the overlays. This anyways needs to change again, once we switch to u-boot SPL booting to boot the target under EFI - which is needed to switch to the A/B rootfs boot via CIP. Tricky stuff. |
|
nice improvements. they pave the way to EFI boot. awesome. thank you! |
I would rather say they are mostly independent. I once implemented the EFI booting for the nanopi-neo target and that was a beast. By EFI booting, we completely leave the raspi boot path with the config files that are loaded by the firmware. Instead, all DTB fixups happen in uboot SPL. The good thing is that u-boot carries the device trees with symbol information, so we don't need to care about what the kernel offers (but we need to keep them at least loosely in sync). |
For details, see the commit messages.
Unfortunately for kernels < 6.5 we still can't use the DTB overlays, as the device tree of the
bcm2711-rpi*targets does not contain the symbol information.