Open jto6 opened 1 year ago
Why would the boot sequence for shared storage look in two places if it is always in the ESP?
It is not always in the ESP (#include
I personally think the goal of 4.2.2 is to provide guidance when authoring images intended to be removable. It should not apply to cases where we are generating tailored OS images (meaning the install process is just a dd and we don't care if the image will be deployed to eMMC or SD card).
As such I thing the proposed wording is definitely an improvement.
Section 4.2.2 states that to make it easier to use stock OS images on removable storage, firmware should be located on the ESP partition (so you don't have to create a dedicated firmware partition).
However, prior in the 4.2 section, it states:
Why would the boot sequence for shared storage look in two places if it is always in the ESP? Or does the statement in 4.2.2 only apply in the case of using a stock OS image?
My suggestion is to reword the sentence in 4.2.2:
to
That way the spec isn't requiring that all removable storage store firmware in the ESP, but only for the cases mentioned to ease the modification of a stock OS image to boot.