From: "Gao, Liming" <liming.gao@intel.com>
To: Supreeth Venkatesh <supreeth.venkatesh@arm.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Achin Gupta <achin.gupta@arm.com>
Subject: Re: [PATCH v4 1/1] MdePkg/Include: Add management mode FV file type and depex.
Date: Fri, 9 Feb 2018 06:03:07 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1CA482@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20180208202516.6067-1-supreeth.venkatesh@arm.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: Supreeth Venkatesh [mailto:supreeth.venkatesh@arm.com]
>Sent: Friday, February 09, 2018 4:25 AM
>To: edk2-devel@lists.01.org
>Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
><liming.gao@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Supreeth
>Venkatesh <supreeth.venkatesh@arm.com>; Achin Gupta
><achin.gupta@arm.com>
>Subject: [PATCH v4 1/1] MdePkg/Include: Add management mode FV file
>type and depex.
>
>As per PI specification v1.6,
>As per section 2.1.4.1,
>The following file types exist:
>Table 3. Defined File Types
>Name Value
>EFI_FV_FILETYPE_RAW 0x01
>EFI_FV_FILETYPE_FREEFORM 0x02
>EFI_FV_FILETYPE_SECURITY_CORE 0x03
>EFI_FV_FILETYPE_PEI_CORE 0x04
>EFI_FV_FILETYPE_DXE_CORE 0x05
>EFI_FV_FILETYPE_PEIM 0x06
>EFI_FV_FILETYPE_DRIVER 0x07
>EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER 0x08
>EFI_FV_FILETYPE_APPLICATION 0x09
>EFI_FV_FILETYPE_MM 0x0A
>EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE 0x0B
>EFI_FV_FILETYPE_COMBINED_MM_DXE 0x0C
>EFI_FV_FILETYPE_MM_CORE 0x0D
>EFI_FV_FILETYPE_MM_STANDALONE 0x0E
>EFI_FV_FILETYPE_MM_CORE_STANDALONE 0x0F
>
>The following new section type is added:
>EFI_SECTION_MM_DEPEX
>
>This patch adds the management mode FV file type and depex.
>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Achin Gupta <achin.gupta@arm.com>
>Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
>Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
>Reviewed-by: Liming Gao <liming.gao@intel.com>
>---
> MdePkg/Include/Pi/PiFirmwareFile.h | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
>diff --git a/MdePkg/Include/Pi/PiFirmwareFile.h
>b/MdePkg/Include/Pi/PiFirmwareFile.h
>index b982c9eda3..16c007fc75 100644
>--- a/MdePkg/Include/Pi/PiFirmwareFile.h
>+++ b/MdePkg/Include/Pi/PiFirmwareFile.h
>@@ -71,10 +71,15 @@ typedef UINT8 EFI_FFS_FILE_STATE;
> #define EFI_FV_FILETYPE_DRIVER 0x07
> #define EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER 0x08
> #define EFI_FV_FILETYPE_APPLICATION 0x09
>-#define EFI_FV_FILETYPE_SMM 0x0A
>+#define EFI_FV_FILETYPE_MM 0x0A
>+#define EFI_FV_FILETYPE_SMM EFI_FV_FILETYPE_MM
> #define EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE 0x0B
>-#define EFI_FV_FILETYPE_COMBINED_SMM_DXE 0x0C
>-#define EFI_FV_FILETYPE_SMM_CORE 0x0D
>+#define EFI_FV_FILETYPE_COMBINED_MM_DXE 0x0C
>+#define EFI_FV_FILETYPE_COMBINED_SMM_DXE
>EFI_FV_FILETYPE_COMBINED_MM_DXE
>+#define EFI_FV_FILETYPE_MM_CORE 0x0D
>+#define EFI_FV_FILETYPE_SMM_CORE EFI_FV_FILETYPE_MM_CORE
>+#define EFI_FV_FILETYPE_MM_STANDALONE 0x0E
>+#define EFI_FV_FILETYPE_MM_CORE_STANDALONE 0x0F
> #define EFI_FV_FILETYPE_OEM_MIN 0xc0
> #define EFI_FV_FILETYPE_OEM_MAX 0xdf
> #define EFI_FV_FILETYPE_DEBUG_MIN 0xe0
>@@ -217,7 +222,8 @@ typedef UINT8 EFI_SECTION_TYPE;
> #define EFI_SECTION_FREEFORM_SUBTYPE_GUID 0x18
> #define EFI_SECTION_RAW 0x19
> #define EFI_SECTION_PEI_DEPEX 0x1B
>-#define EFI_SECTION_SMM_DEPEX 0x1C
>+#define EFI_SECTION_MM_DEPEX 0x1C
>+#define EFI_SECTION_SMM_DEPEX EFI_SECTION_MM_DEPEX
>
> ///
> /// Common section header.
>--
>2.14.1
prev parent reply other threads:[~2018-02-09 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 20:25 [PATCH v4 1/1] MdePkg/Include: Add management mode FV file type and depex Supreeth Venkatesh
2018-02-09 6:03 ` Gao, Liming [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14E1CA482@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox