From d8c463a04f8f987b997c0ec70dd548207873633d Mon Sep 17 00:00:00 2001 From: Konstantin Aladyshev Date: Fri, 15 Jul 2022 20:56:52 +0300 Subject: Update information about FV region --- Lessons_uncategorized/Lesson_FDF/README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'Lessons_uncategorized/Lesson_FDF/README.md') diff --git a/Lessons_uncategorized/Lesson_FDF/README.md b/Lessons_uncategorized/Lesson_FDF/README.md index bc6bd70..b51e3d5 100644 --- a/Lessons_uncategorized/Lesson_FDF/README.md +++ b/Lessons_uncategorized/Lesson_FDF/README.md @@ -367,7 +367,7 @@ Here are some explanation for the most common ones: `FV`, `DATA`, `FILE`: ## FV region -The `FV` region type is a pointer to some `Firmware Volume`. `Firmware Volume` (`FV`) is a data block next level lower than `Flash Device Image` (`FD`). +The `FV` region type is a pointer to some `Firmware Volume`. `Firmware Volume` (`FV`) is a region with a filesystem inside. Formatting of this region is defined by the `UEFI Platform Initialization (PI) specification (Volume 3: Shared Architectural Elements)`. We will look at the `Firmware Volumes` in the next lesson. Example: ``` @@ -376,8 +376,6 @@ FV = FVMAIN ``` In this case FDF must define the section `[FV.FVMAIN]`. -We will look at the `Firmware Volumes` in the next lesson. - ## DATA region In the case of a `DATA` region we immediately define the data inside the region via initialized array: -- cgit v1.2.3-18-g5258