EFI_FFS_VOLUME_TOP_FILE_GUID. The file name is a GUID, and
EFI_FFS_VOLUME_TOP_FILE_GUIDis the C define that is used by code and the build system in place of the GUID value.
.reloc) section of security executables may be stripped.
.relocsection stripped for size optimization and module cannot be compressed - the images must be re-based to the location in ROM.
.relocsection stripped. The EDK II build system uses a keyword,
SHADOW, in the module's INF file to indicate this mode, setting
SHADOW = TRUE. By default, the EDK II build system will strip the
.relocsection of PEIMs; PEIMs must specify the
SHADOW = TRUEin the module's INF file to prevent this. Additional flags in the FDF file,
RELOCS_STRIPPED, are provided to over-ride stripping of the
EFI_SECTION_PEI_DEPEXsection is used to define the dependency relationship. The PEI Foundation will use this section (if present in an FFS) to ensure the required PEIMs are available prior to dispatch.
.relocsection stripped. Additionally, compression of these modules may decrease the overall size of the FD image in hardware. Using the terse image format for drivers of this type is not permitted by the PI specification. For this class of driver, one PEI and/or one DXE dependency section can be added to the FFS file containing the image.
.relocsection from these modules and any UEFI applications is not recommended, but is allowed in certain cases. Additionally, these images cannot be converted to the terse format - only elements of the PEI Foundation (PEI Core) and PEIMs can be converted to use the terse format headers. Compression of the images is permitted, however, as most compression algorithms work better over a larger data set, it is recommended that the images be combined into a Firmware Volume, and the entire FV can be compressed.
EFI_SECTION_PEI_DEPEXsection, a dependency
EFI_SECTION_DXE_DEPEXsection may be required. These files are used by the DXE foundation to ensure required drivers are available when needed.