[if gte mso 9]>

Re: [edk2] Adding EFI_SECTION directly to ffs

Subject: Re: [edk2] Adding EFI_SECTION directly to ffs

From: "Hauch, Larry" <larry.hauch@intel.com>

To: "edk2-devel@lists.sourceforge.net" <edk2-devel@lists.sourceforge.net>

Date: 2012-01-31 01:43:09

Hi Justin,


The SEC_BIN stands for code executing during the PI Security Phase, not a binary with a section header prepended.

The EDK II Build system currently treats SEC_BIN as a security binary, requiring the tools to run the GenSec tool on the binary, processing the file to get the correct alignment.

However, we will investigate the possibility of supporting a binary file which already has the EFI section header.





From: Justin Johnson [mailto:justinj@ami.com]
Sent: Thursday, January 26, 2012 12:22 PM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Adding EFI_SECTION directly to ffs



I have a tool which builds a section file, of type EFI_SECTION_FREEFORM_SUBTYPE_GUID. That is, the binary file already has the section header prepended. What needs to be entered in the FDF so that GenSec is not run on this binary file. It should just be included as an input to GenFfs.



I have tried both:

RAW       SEC_BIN                 Optional $(INF_OUTPUT)/$(MODULE_NAME).sec


RAW       BIN                     Optional $(INF_OUTPUT)/$(MODULE_NAME).sec


But both entries will still cause GenSec to be run on $(MODULE_NAME).sec.



Justin Johnson

Associate BIOS Engineer

American Megatrends, Inc.


The information contained in this message may be confidential and proprietary to American Megatrends, Inc.  This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited.  Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.