diff options
| author | Dun Tan <dun.tan@intel.com> | 2021-09-01 10:29:41 +0800 |
|---|---|---|
| committer | Patrick Georgi <pgeorgi@google.com> | 2021-09-02 06:07:08 +0000 |
| commit | 4a359401370d179b6b37dd6a6ff0c87ca8e1d241 (patch) | |
| tree | 8049dd86a51f807de38965174f63994e34b0855a /util/cbfstool/fv.h | |
| parent | 6f3fd6358f605c181f958ded9ef92803cec172fd (diff) | |
| download | coreboot-4a359401370d179b6b37dd6a6ff0c87ca8e1d241.tar.gz coreboot-4a359401370d179b6b37dd6a6ff0c87ca8e1d241.tar.bz2 coreboot-4a359401370d179b6b37dd6a6ff0c87ca8e1d241.zip | |
util/cbftool: Fix the bug in parsing Uefipayload with extended header
The patch is to fix "Not a usable UEFI firmware volume" issue when
creating CBFS/flash image. This issue is caused by adding FvNameGuid
in UefiPayloadEntry.fdf in EDKII. There is an ext header between header
of Fv and header of PayloadEntry in Fv with FvNameGuid. The ext header
causes the UefiPayloadEntry to be found incorrectly when parsing Fv.
Commit in EDKII: 4bac086e8e007c7143e33f87bb96238326d1d6ba
Bugzila: https://bugzilla.tianocore.org/show_bug.cgi?id=3585
Signed-off-by: Dun Tan <dun.tan@intel.com>
Change-Id: Id063efb1c8e6c7a96ec2182e87b71c7e8b7b6423
Reviewed-on: https://review.coreboot.org/c/coreboot/+/57296
Reviewed-by: Ray Ni <ray.ni@intel.com>
Reviewed-by: King Sumo <kingsumos@gmail.com>
Reviewed-by: Patrick Rudolph <siro@das-labor.org>
Reviewed-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'util/cbfstool/fv.h')
| -rw-r--r-- | util/cbfstool/fv.h | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/util/cbfstool/fv.h b/util/cbfstool/fv.h index 21bd89f56350..0ad650f1babf 100644 --- a/util/cbfstool/fv.h +++ b/util/cbfstool/fv.h @@ -32,3 +32,8 @@ typedef struct { uint8_t size[3]; uint8_t section_type; } common_section_header_t; + +typedef struct { + uint8_t guid[16]; + uint32_t ext_header_size; +} firmware_volume_ext_header_t; |