EFI SECTION TYPE
From PhoenixWiki
Prototype
typedef UINT8 EFI_SECTION_TYPE;
#define EFI_SECTION_ALL 0x00 #define EFI_SECTION_COMPRESSION 0x01 #define EFI_SECTION_GUID_DEFINED 0x02 #define EFI_SECTION_DISPOSABLE 0x03 #define EFI_SECTION_PE32 0x10 #define EFI_SECTION_PIC 0x11 #define EFI_SECTION_DXE_DEPEX 0x13 #define EFI_SECTION_COMPATIBILITY16 0x16 #define EFI_SECTION_FIRMWARE_VOLUME_IMAGE 0x17 #define EFI_SECTION_FREEFORM_SUBTYPE_GUID 0x18 #define EFI_SECTION_RAW 0x19 #define EFI_SECTION_PEI_DEPEX 0x1B
Description
| Name | Description | Structure |
|---|---|---|
| EFI_SECTION_ALL | The section type EFI_SECTION_ALL is a pseudo type. It is used as a wild card when retrieving sections. The section type EFI_SECTION_ALL matches all section types. | None |
| EFI_SECTION_COMPATIBILITY16 | A Compatibility16 image section is a leaf section that contains an IA-32 16-bit executable image. IA-32 16-bit legacy code that may be included in PI Architecture firmware is stored in a 16-bit executable image. | None |
| EFI_SECTION_COMPRESSION | A compression section is an encapsulation section in which the section data is compressed. To process the contents and extract the enclosed section stream, the section data must be decompressed using the decompressor indicated by the CompressionType parameter. The decompressed image is then interpreted as a section stream. | EFI_COMPRESSION_SECTION |
| EFI_SECTION_DISPOSABLE | A disposable section is an encapsulation section in which the section data may be disposed of during the process of creating or updating a firmware image without significant impact on the usefulness of the file. The Type field in the section header is set to EFI_SECTION_DISPOSABLE. This allows optional or descriptive data to be included with the firmware file which can be removed in order to conserve space. The contents of this section are implementation specific, but might contain debug data or detailed integration instructions. | None |
| EFI_SECTION_DXE_DEPEX | The DXE dependency expression section is a leaf section that contains a dependency expression that is used to determine the dispatch order for a DXE driver. | None |
| EFI_SECTION_GUID_DEFINED | A GUID-defined section contains a section-type-specific header that contains an identifying GUID, followed by an arbitrary amount of data. It is an encapsulation section in which the method of encapsulation is defined by the GUID. The GUID-defined section enables custom encapsulation section types for any purpose. One commonly expected use is creating an encapsulation section to enable a cryptographic authentication of the section contents. | EFI_GUID_DEFINED_SECTION |
| EFI_SECTION_PE32 | The PE32+ image section is a leaf section that contains a complete PE32+ image. Normal UEFI executables are stored within PE32+ images. | None |
| EFI_SECTION_PIC | A PIC image section is a leaf section that contains a position-independent-code (PIC) image. In addition to normal PE32+ images that contain relocation information, PEIM executables may be PIC and are referred to as PIC images. A PIC image is the same as a PE32+ image except that all relocation information has been stripped from the image and the image can be moved and will execute correctly without performing any relocation or other fix-ups. | None |
| EFI_SECTION_TE | The terse executable section is a leaf section that contains a Terse Executable (TE) image. A TE image is an executable image format specific to the PI Architecture that is used for storing executable images in a smaller amount of space than would be required by a full PE32+ image. Only PEI Foundation and PEIM files may contain a TE section. | None |
| EFI_SECTION_USER_INTERFACE | The user interface file name section is a leaf section that contains a Unicode string that contains a human-readable file name. This section is optional and is not required for any file types. There must never be more than one user interface file name section contained within a file. | EFI_USER_INTERFACE_SECTION |
| EFI_SECTION_VERSION | A version section is a leaf section that contains a numeric build number and an optional Unicode string that represents the file revision. To facilitate versioning of PEIMs, DXE drivers, and other files, a version section may be included in a file. There must never be more than one version section contained within a file. | EFI_VERSION_SECTION |
| EFI_SECTION_FIRMWARE_VOLUME_IMAGE | A firmware volume image section is a leaf section that contains a Firmware Volume Image. | None |
| EFI_SECTION_FREEFORM_SUBTYPE_GUID | A free-form subtype GUID section is a leaf section that contains a single EFI_GUID. It is typically used in files of type EFI_FV_FILETYPE_FREEFORM to provide an extensibility mechanism for file types. | EFI_FREEFORM_SUBTYPE_GUID_SECTION |
| EFI_SECTION_RAW | A raw section is a leaf section that contains an array of zero or more bytes. No particular formatting of these bytes is implied by this section type. | None |
| EFI_SECTION_PEI_DEPEX | The PEI dependency expression section is a leaf section that contains a dependency expression that is used to determine dispatch order for a PEIM. | None |
Copyright (C) 2008 Phoenix Technologies Ltd. All Rights Reserved. Portions copyright © 2006 UEFI Forum, Inc. Used with permission.
