diff options
| author | Mathew McBride <matt@traverse.com.au> | 2021-06-01 01:48:25 +0000 |
|---|---|---|
| committer | Petr Štetiar <ynezz@true.cz> | 2023-06-13 14:12:29 +0200 |
| commit | 04d2f8f11fc4c1809c297b5b90fddbad98ce905d (patch) | |
| tree | ccc0ab0cce9cdc8c2fbead353e77a9293d631ab6 /target/linux | |
| parent | b0e724e49c110d1f36e475186ad945da70829817 (diff) | |
| download | upstream-04d2f8f11fc4c1809c297b5b90fddbad98ce905d.tar.gz upstream-04d2f8f11fc4c1809c297b5b90fddbad98ce905d.tar.bz2 upstream-04d2f8f11fc4c1809c297b5b90fddbad98ce905d.zip | |
build: use 128MiB as the boot/kernel partition size on armvirt target
The nominal partition type for EFI boot partitions is FAT32,
which has a minimum size of 32MiB on a 512-byte-sector block device.
To ensure that the boot partition is created as FAT32 set a size
well above this minimum.
A useful discussion about EFI partition sizes can be found here:
https://superuser.com/questions/1310927/what-is-the-absolute-minimum-size-a-uefi-system-partition-can-be
I have found 128MiB works pretty consistently across both
tools (mkfs.fat) and firmwares (EDKII)
Signed-off-by: Mathew McBride <matt@traverse.com.au>
(cherry picked from commit 71e56b2ff1e8aeb3205784c0b5f8ca6ba0fbbf63)
Diffstat (limited to 'target/linux')
0 files changed, 0 insertions, 0 deletions