Attention is currently required from: Patrick Rudolph, Dun Tan. Paul Menzel has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/57296 )
Change subject: util/cbftool: Fix the bug in parsing Uefipayload with extended header ......................................................................
Patch Set 3:
(5 comments)
Commit Message:
https://review.coreboot.org/c/coreboot/+/57296/comment/6cddf87a_b7146ee8 PS3, Line 7: Fix the bug Fix bug
https://review.coreboot.org/c/coreboot/+/57296/comment/6ca1d04c_659b6a9c PS3, Line 7: cbftool cbfstool
https://review.coreboot.org/c/coreboot/+/57296/comment/455d85c0_22a4c6e6 PS3, Line 7: Uefipayload UefiPayload
https://review.coreboot.org/c/coreboot/+/57296/comment/baafd061_7421730c PS3, Line 9: The patch is to fix "Not a usable UEFI firmware volume" issue when : creating CBFS/flash image. Is that documented somewhere? Please add a reference, or elaborate how to reproduce this. I am also curious, because a lot of people are using this, I think, and I have not heard about the problem yet.
https://review.coreboot.org/c/coreboot/+/57296/comment/563d7e9d_0ed806fa PS3, Line 10: 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. Is that a recent change in UefiPayload?