Comment # 4 on bug 1177358 from Ancor Gonzalez Sosa

Working on this right now. The CURRENT criteria to decide the EFI sizes is
this[1]:

When proposing a new EFI partition in x86
 - when aiming for the recommended size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be exactly 500 MiB large
 - when aiming for the minimal size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be at least 256 MiB
   * requires /boot/efi to be at most 500 MiB

When proposing a new EFI partition in aarch64 (including Raspberry Pi)
 - when aiming for the recommended size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be exactly 256 MiB large
 - when aiming for the minimal size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be exactly 256 MiB large

I'm changing that to work like this:

When proposing a new EFI partition in x86
 - when aiming for the recommended size
   * requires /boot/efi it to use FAT32
   * requires /boot/efi to be at least 256 MiB
   * requires /boot/efi to be at most 512 MiB
 - when aiming for the minimal size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be at least 128 MiB
   * requires /boot/efi to be at most 512 MiB

When proposing a new EFI partition in aarch64 (including Raspberry Pi)
 - when aiming for the recommended size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be exactly 128 MiB large
 - when aiming for the minimal size
   * does not enforce FAT32 or 16 (FAT size will be decided by mkfs.vfat)
   * requires /boot/efi to be exactly 128 MiB large

[1] Extracted from the automatically-generated document at
https://github.com/yast/yast-storage-ng/blob/master/doc/boot-requirements.md