Closed hnez closed 8 months ago
I've tried to implement two more elegant approaches to what is in this PR, but they did not work out:
/dev/zero
in the genimage config did not clear the stateWhat is new is that we no longer rely on partition numbers in the boot process and instead use partition labels in barebox. This allows us to change the partition numbering. This PR already uses that to remove the reserved
partition and a later PR can use it again to add the barebox partitions to the partition table.
I've made sure that the testsuite succeeds and would suggest merging the PR as-is.
The bootchooser info stored in the barebox state does not make any sense after installing a fresh image via
fastboot
(see the removedREADME.md
section for more details).Make sure the barebox state part of the
emmc-image-lxatac.simg
sparse image was touched during image generation so it is not marked as sparse and thus skipped when flashing.There are also preparations to expose the barebox state as a partition with the correct type
UUID
, but that requires some changes to the barebox devicetree because as of now it tries to add the state twice and fails the second time.Todo before merging:
root-a
,root-b
,data
) did not shift around and their alignment is still the same. 2023-11-10: Partition numbering did indeed change, but this is less of a problem now that we have label-based boot slot selection.