From: Marvin H?user <Marvin.Haeuser@outlook.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Supreeth Venkatesh <supreeth.venkatesh@arm.com>,
"michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
"liming.gao@intel.com" <liming.gao@intel.com>
Subject: Re: [PATCH v1 1/1] MdePkg/Include: Add management mode FV file type and depex.
Date: Wed, 24 Jan 2018 00:34:18 +0000 [thread overview]
Message-ID: <AM4PR06MB14915A67E0057E79F30C467C80E20@AM4PR06MB1491.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <20180123200303.5547-1-supreeth.venkatesh@arm.com>
Good day,
I noticed this patch lacks the definition of "EFI_FV_FILETYPE_MM_CORE" (0x0C).
Furthermore, may I suggest changing the *_SMM_* definitions to be defined via the *_MM_* definitions?
Best regards,
Marvin.
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Supreeth Venkatesh
> Sent: Tuesday, January 23, 2018 9:03 PM
> To: edk2-devel@lists.01.org
> Cc: michael.d.kinney@intel.com; liming.gao@intel.com
> Subject: [edk2] [PATCH v1 1/1] MdePkg/Include: Add management mode FV
> file type and depex.
>
> As per PI specification v1.6,
> The following new file types are added:
> EFI_FV_FILETYPE_MM_STANDALONE
> EFI_FV_FILETYPE_MM_CORE_STANDALONE
>
> 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>
> ---
> MdePkg/Include/Pi/PiFirmwareFile.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/MdePkg/Include/Pi/PiFirmwareFile.h
> b/MdePkg/Include/Pi/PiFirmwareFile.h
> index b982c9eda3..6086d1bb2f 100644
> --- a/MdePkg/Include/Pi/PiFirmwareFile.h
> +++ b/MdePkg/Include/Pi/PiFirmwareFile.h
> @@ -72,9 +72,12 @@ typedef UINT8 EFI_FFS_FILE_STATE; #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_FIRMWARE_VOLUME_IMAGE 0x0B
> #define EFI_FV_FILETYPE_COMBINED_SMM_DXE 0x0C
> +#define EFI_FV_FILETYPE_COMBINED_MM_DXE 0x0C
> #define EFI_FV_FILETYPE_SMM_CORE 0x0D
> +#define EFI_FV_FILETYPE_MM_STANDALONE 0x0E
> #define EFI_FV_FILETYPE_OEM_MIN 0xc0
> #define EFI_FV_FILETYPE_OEM_MAX 0xdf
> #define EFI_FV_FILETYPE_DEBUG_MIN 0xe0
> @@ -218,6 +221,7 @@ typedef UINT8 EFI_SECTION_TYPE;
> #define EFI_SECTION_RAW 0x19
> #define EFI_SECTION_PEI_DEPEX 0x1B
> #define EFI_SECTION_SMM_DEPEX 0x1C
> +#define EFI_SECTION_MM_DEPEX 0x1C
>
> ///
> /// Common section header.
> --
> 2.14.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-01-24 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 20:03 [PATCH v1 1/1] MdePkg/Include: Add management mode FV file type and depex Supreeth Venkatesh
2018-01-24 0:34 ` Marvin H?user [this message]
2018-01-25 17:45 ` Supreeth Venkatesh
2018-01-25 17:52 ` Tim Lewis
2018-01-25 18:31 ` Marvin H?user
2018-01-25 21:20 ` Supreeth Venkatesh
2018-01-29 14:55 ` Gao, Liming
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=AM4PR06MB14915A67E0057E79F30C467C80E20@AM4PR06MB1491.eurprd06.prod.outlook.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