summaryrefslogtreecommitdiff
path: root/src/mainboard/google/fizz/chromeos.fmd
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2019-03-04 14:28:37 +0800
committerPatrick Georgi <pgeorgi@google.com>2019-03-05 19:31:43 +0000
commit9497fcb742cebafb8d47f4cc3f0da796b0490498 (patch)
treeac57f48fb65ab7e5d3831509b7d7cd57f90dd4ff /src/mainboard/google/fizz/chromeos.fmd
parent7362768c5097249bf8823d5c4446804f3ccd87e6 (diff)
downloadcoreboot-9497fcb742cebafb8d47f4cc3f0da796b0490498.tar.xz
cbfstool: Change FMD annotation to flags
The idea of "annotation" for firmware sections was pretty flexible, but in future we will want multiple attributes applied to same area. For example, indicate the section must be preserved when updating firmware so serial number or MAC address can be preserved. The solution here is to extend annotation so it can take multiple identifiers (flags) in a row. For example, to declare a 64KB COREBOOT section as CBFS using annotation: COREBOOT(CBFS)@0x0 64k If there's a new flag "PRESERVE" indicating the section must be preserved before update, we can declare it following CBFS flag: COREBOOT(CBFS PRESERVE)@0x0 64k The flags are directly parsed in fmd_parser, and stored in an union flashmap_flags. Output modules can choose to ignore or process the flags. Currently the only supported flag is "CBFS" (for backward compatible with annotation). There will be more new flags in follow up patches. BUG=chromium:936768 TEST=make; boots on x86 "google/eve" and arm "google/kukui" devices Change-Id: Ie2d99f570e6faff6ed3a4344d6af7526a4515fae Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/31706 Reviewed-by: Julius Werner <jwerner@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/google/fizz/chromeos.fmd')
0 files changed, 0 insertions, 0 deletions