Hi Marcin,
On 23/10/2024 at 11:46, Marcin Juszkiewicz wrote:
For that first 16MB partition it would be nice to use GPT type EF02
(BIOS boot partition) so partitioning tools will see that it is
partition for bootloaders.
Partitioning tools do not really care about what a partition is for.
AFAIK the "BIOS boot" type is used only by GRUB for BIOS on x86.
Does U-Boot or any other arm64 boot loader use this type ?
I know this is very specific, but using the "BIOS boot" type for the
16MiB reserved partition would get in the way of a multi-boot x86+arm64
installation because GRUB for BIOS is written at the beginning (30-100
kB) of the BIOS boot partition. Is this a realistic use case ?
Separate /boot/ is handy if user wants to have / on LVM (crypted or
not) as this allows 'OS loader' (grub-efi in Debian) to load kernel,
initramfs (and dtb if needed) from /boot and start the OS.
GRUB can read LVM and does not require a separate /boot. Anyway
automatic partitioning built-in recipes create a separate /boot when
partitioning with LVM (encrypted or not).
If hardware does not handle EFI variables (so we can not store
BootOrder vars) then /efi/boot/bootaa64.efi should be written as this
is default name for OS loader in EFI/aarch64 world.
If EFI variables are read-only or not available, grub-installer prompts
the user to install GRUB in the removable media path and/or update EFI
boot variables.
