Likely not important for the broader discussion, but a small note which may help with the solution space. On Tuesday, 1 February 2022 00:29:08 CET Ben Hutchings wrote: > I'm not sure how common it is to make the EFI boot partition be /boot. I make images for my Pine64 Rock64 which has its EFI partition mounted on /boot/efi (and I set the 'esp' and 'boot' flags on that partition). This should work on all rockchip based SoC's, but only verified it on Rock64. I use the grub-efi-arm64 package. > I do know Raspberry Pi users expect /boot to be the FAT partition that > its boot ROM uses, and it is a common complaint that our linux-image > packages are not upgradable in such a configuration. That's an unfortunate *choice* by the Raspberry Pi foundation, but there is no need for that. The RPi (initial) boot loader looks for the first FAT partition to find the files needed for the later stage of the boot process. It does not care where that is mounted (or whether it is mounted at all). On the RPi images on raspi.debian.net the FAT partition is mounted on /boot/firmware (and raspi-firmware package expects them there). HTH, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.