Commit Graph

9 Commits

Author SHA1 Message Date
1ac3f3ab0a
fix partition table 2023-10-16 11:04:42 +05:30
a21075fd8f
forgot to move the log in the appliance dir 2023-10-16 10:44:31 +05:30
2d2ee0a676
start the first partition with a 32MiB "offset"
Since Kickstart no longer has the '--start' and '--end' options for the
partition command, we need to do this manually.
3e655d4c5d

Why do we need to do this at all? Well, because some SoCs read U-Boot
from the boot media at a particular offset. Normally, the first
partition starts at 2048 (with fdisk) or at 8192 (if using Kickstart)
which means that something from the first partition will be erased, or
data written here will eventually overwrite U-Boot if U-Boot is greater
than 2MiB.

Looking at the biggest file in 'uboot-images-armv8' package, the biggest
file is ~12 MiB so the double of closest 2's exponent results in 32MiB.
2023-10-16 09:21:42 +05:30
cbbee2dbbe
revert from two images to only a single image (GPT) 2023-10-16 08:08:05 +05:30
1fde830d55
create shasums for .raw.zst files too 2023-10-10 11:16:48 +05:30
15c5e5afcb
Create GPT and MBR images
Some SBCs, like the Raspberry Pi (at least up-to RPi4) lineup needs MBR
partitioned disks, while other, more newer SBCs, like the Orange Pi 5,
needs GPT partitioned disks. So create two disk images.
2023-10-10 11:06:09 +05:30
c5277b0a10
chown the output directory 2023-10-09 09:06:15 +05:30
ae3ff359cc
move the log inside the appliance dir 2023-10-04 14:45:18 +05:30
fcd8a0ef79
init commit 2023-09-13 06:59:56 +05:30