Liming - Your e-mail answers part of my concern. The other part is: normally, changes to critical components are reviewed by the entire open-source community before they are checked in, not after. This is a new feature, with wide-ranging implications.
Tim From: Gao, Liming [mailto:liming....@intel.com] Sent: Sunday, June 14, 2015 11:01 PM To: edk2-devel@lists.sourceforge.net Subject: Re: [edk2] FV FvName in FV Ext Entry Tim: Yes. We will update EDKII FDF and Build spec to describe this change. When the FvNameGuid entry is present in an [FV] section, the tools will generate an FvNameString entry in FV EXT header using the UiFvName. That means FvNameGuid and FvNameString will both be generated or not. Thanks Liming From: Tim Lewis [mailto:tim.le...@insyde.com] Sent: Friday, June 12, 2015 9:56 AM To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net> Subject: [edk2] FV FvName in FV Ext Entry Would someone care to document the changes that were made to add the FV Name to the FV volume header? It would be helpful for other folks to know what Intel is planning here, and how it fits in with the overall scheme. Also, how to turn off this feature so that it is not generated. Thanks, Tim
------------------------------------------------------------------------------
_______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
