Jeremy Jackson has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/42028 )
Change subject: Create separate .config files in CBFS for fallback/normal prefixes ......................................................................
Patch Set 3:
Patch Set 3:
OT: I wonder how the board status script `util/board_status/board_status.sh` could detect, what prefix was used for booting. Can that be determined from the shell?
That is on my mind as well. After reading about FMAP regions and vboot implementation, I think the full scope should be, how to determine what region (vboot case currently), prefix, and bootblock (Intel top-swap case) was booted from. This patch is meant to address the related question of "what was the build configuration of" what was booted.
Knowing what was booted from helps board_status.sh, and enables testing using alternate bootblock and normal prefix, leaving default top bootblock and fallback prefix for recovery.
I think other areas may benefit from knowing what was booted from, starting with the bootblock itsself. I see the top-swap feature as a valueable tool. Using knowledge of what bootblock is in use (CMOS top-swap bit BUCTS), may replace or be used in combination with the CMOS bit for normal/fallback selection.
Additionally, knowing what *wasn't* booted and the configuration(s) may enable things like fwupd or other means of automated updates.
I don't have a patch ready, so what's the best way to move this discussion to a new thread? ML or make up a trivial patch to start a gerrit thread?