aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKonstantin Aladyshev <aladyshev22@gmail.com>2022-07-21 18:48:59 +0300
committerKonstantin Aladyshev <aladyshev22@gmail.com>2022-07-21 18:48:59 +0300
commitcd84ee36238af75ad77b95f6ddeea41af15ded77 (patch)
tree8f7465a1a455d7c6a48c442491960d6a72e6969c
parent0fa556bb69cc7c9d4d62dfd7a1df056c7cd04a27 (diff)
downloadUEFI-Lessons-cd84ee36238af75ad77b95f6ddeea41af15ded77.tar.gz
UEFI-Lessons-cd84ee36238af75ad77b95f6ddeea41af15ded77.tar.bz2
UEFI-Lessons-cd84ee36238af75ad77b95f6ddeea41af15ded77.zip
Drop the FILE section info from the first FV lesson
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
-rw-r--r--Lessons_uncategorized/Lesson_FDF_FV/README.md40
1 files changed, 0 insertions, 40 deletions
diff --git a/Lessons_uncategorized/Lesson_FDF_FV/README.md b/Lessons_uncategorized/Lesson_FDF_FV/README.md
index 00b78b2..433b21b 100644
--- a/Lessons_uncategorized/Lesson_FDF_FV/README.md
+++ b/Lessons_uncategorized/Lesson_FDF_FV/README.md
@@ -122,46 +122,6 @@ The data inside the file is formatted with respect to the `EFI_FFS_FILE_HEADER.T
| EFI_FV_FILETYPE_FFS_PAD | 0xF0 | Pad File For FFS |
-Almost each type of file consists of sections, with each section prepended with a header `EFI_COMMON_SECTION_HEADER` ([https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Pi/PiFirmwareFile.h](https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Pi/PiFirmwareFile.h)):
-```
-EFI_COMMON_SECTION_HEADER
-
-Summary:
-Defines the common header for all the section types
-
-Prototype:
-typedef struct {
- UINT8 Size[3];
- EFI_SECTION_TYPE Type;
-} EFI_COMMON_SECTION_HEADER;
-
-Parameters:
-Size A 24-bit unsigned integer that contains the total size of the section in bytes, including the EFI_COMMON_SECTION_HEADER
-Type Declares the section type
-
-Description:
-The type EFI_COMMON_SECTION_HEADER defines the common header for all the section types
-```
-
-Specification defines following sections:
-| Name | Value | Description |
-| ---- | ----- | ----------- |
-| EFI_SECTION_COMPRESSION | 0x01 | Encapsulation section where other sections are compressed |
-| EFI_SECTION_GUID_DEFINED | 0x02 | Encapsulation section where other sections have format defined by a GUID |
-| EFI_SECTION_DISPOSABLE | 0x03 | Encapsulation section used during the build process but not required for execution |
-| EFI_SECTION_PE32 | 0x10 | PE32+ Executable image |
-| EFI_SECTION_PIC | 0x11 | Position-Independent Code |
-| EFI_SECTION_TE | 0x12 | Terse Executable image |
-| EFI_SECTION_DXE_DEPEX | 0x13 | DXE Dependency Expression |
-| EFI_SECTION_VERSION | 0x14 | Version, Text and Numeric |
-| EFI_SECTION_USER_INTERFACE | 0x15 | User-Friendly name of the driver |
-| EFI_SECTION_COMPATIBILITY16 | 0x16 | DOS-style 16-bit EXE |
-| EFI_SECTION_FIRMWARE_VOLUME_IMAGE | 0x17 | PI Firmware Volume image |
-| EFI_SECTION_FREEFORM_SUBTYPE_GUID | 0x18 | Raw data with GUID in header to define format |
-| EFI_SECTION_RAW | 0x19 | Raw data |
-| EFI_SECTION_PEI_DEPEX | 0x1b | PEI Dependency Expression |
-| EFI_SECTION_MM_DEPEX | 0x1c | Leaf section type for determining the dispatch order for an MM Traditional driver in MM Traditional Mode or MM Standaline driver in MM Standalone Mode |
-
# Create simple Firmware Volume
Now let's try to create the most simple firmware volume which would contain one binary file. Here is code for this structure (`UefiLessonsPkg/UefiLessonsPkg.fdf`):