public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Shaw, Kevin W" <kevin.w.shaw@intel.com>
Subject: Re: [Patch] FDF Spec: Per PI 1.6 to support FV extended header contain FV used size
Date: Sat, 30 Sep 2017 05:23:00 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1671C6@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1506579696-16236-1-git-send-email-yonghong.zhu@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Zhu, Yonghong
>Sent: Thursday, September 28, 2017 2:22 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
><michael.d.kinney@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
>Subject: [Patch] FDF Spec: Per PI 1.6 to support FV extended header contain
>FV used size
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Michael Kinney <michael.d.kinney@intel.com>
>Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>---
> 2_fdf_design_discussion/25_[fv]_sections.md  | 2 +-
> 3_edk_ii_fdf_file_format/36_[fv]_sections.md | 2 ++
> README.md                                    | 1 +
> 3 files changed, 4 insertions(+), 1 deletion(-)
>
>diff --git a/2_fdf_design_discussion/25_[fv]_sections.md
>b/2_fdf_design_discussion/25_[fv]_sections.md
>index 82755dd..7b50017 100644
>--- a/2_fdf_design_discussion/25_[fv]_sections.md
>+++ b/2_fdf_design_discussion/25_[fv]_sections.md
>@@ -57,11 +57,11 @@ previously defined sections within another FV section.
>This eliminates the need
> to re-specify components or modules in multiple places. When the
>`FvNameString`
> entry is present and set to TRUE in an `[FV]` section, the tools will generate
> an `FvNameString` entry in FV EXT header using the `UiFvName`.
>
> This section also specifies how to define content for PI FV Extensions which
>-provides a mapping between a GUID and an OEM file type. The size of
>+provides a mapping for a GUID, an OEM file type and FV used size. The size
>of
> `EFI_FIRMWARE_VOLUME_EXT_HEADER` and
>`EFI_FIRMWARE_VOLUME_EXT_ENTRY` sizes will
> be calculated based on content, while the
>`EFI_FIRMWARE_VOLUME_EXT_ENTRY` type
> must be defined by the platform integrator based on the PI specification,
> volume 3 The content is limited to the contents of a binary file specified by a
> FILE statement or a data array specified by a `DATA` statement.
>diff --git a/3_edk_ii_fdf_file_format/36_[fv]_sections.md
>b/3_edk_ii_fdf_file_format/36_[fv]_sections.md
>index f2d34cf..b4f292a 100644
>--- a/3_edk_ii_fdf_file_format/36_[fv]_sections.md
>+++ b/3_edk_ii_fdf_file_format/36_[fv]_sections.md
>@@ -74,10 +74,11 @@ Conditional statements may be used anywhere within
>this section.
> <FvStatements>      ::= [<BlockStatements>]
>                         [<FvAlignment>]
>                         [<FvAttributes>]
>                         [<FileSystemGuid>]
>                         [<FvNameGuid>]
>+                        [<FvUsedSize>]
>                         [<FvNameString>]
>                         [<PeiAprioriSection>]
>                         [<DxeAprioriSection>]
>                         <InfStatements>*
>                         <FileStatements>*
>@@ -108,10 +109,11 @@ Conditional statements may be used anywhere
>within this section.
>                         [<TS> "READ_DISABLED_CAP" <Eq> <TrueFalse> <EOL>]
>                         [<TS> "READ_STATUS" <Eq> <TrueFalse> <EOL>]
>                         [<TS> "ERASE_POLARITY" <Eq> {"0"} {"1"} <EOL>]
> <FileSystemGuid>    ::= <TS> "FileSystemGuid" <Eq> <NamedGuid> <EOL>
> <FvNameGuid>        ::= <TS> "FvNameGuid" <Eq> <NamedGuid> <EOL>
>+<FvUsedSize>        ::= <TS> "FvUsedSizeEnable" <Eq> <TrueFalse> <EOL>
> <FvNameString>      ::= <TS> "FvNameString" <Eq> <TrueFalse> <EOL>
> <PeiAprioriSection> ::= <TS> "APRIORI" <MTS> "PEI" <MTS>
>                         "{" <EOL>
>                         <MacroDefinition>*
>                         <InfStatements>*
>diff --git a/README.md b/README.md
>index 71c92fc..4e15a73 100644
>--- a/README.md
>+++ b/README.md
>@@ -207,5 +207,6 @@ Copyright (c) 2006-2017, Intel Corporation. All rights
>reserved.
> |            | [#478](https://bugzilla.tianocore.org/show_bug.cgi?id=478) FDF
>spec: extend the <FmpFileData> to support <FvStatements> and
><FdStatenents>                                 |               |
> |            | [#353](https://bugzilla.tianocore.org/show_bug.cgi?id=353) Build
>spec: Allow nested includes in DSC and FDF files                                                          |
>|
> |            | [#520](https://bugzilla.tianocore.org/show_bug.cgi?id=520) FDF
>spec: Update Precedence of PCD Values                                                                       |
>|
> |            | [#585](https://bugzilla.tianocore.org/show_bug.cgi?id=585) FDF
>Spec: Update the FDF_SPECIFICATION version to 0x0001001B or 1.27
>|               |
> |            | Per PI 1.6 to extend FFS alignment to 16M
>|               |
>+|            | Per PI 1.6 to support FV extended header entry contain the used
>size of FV                                                                                                 |               |
>--
>2.6.1.windows.1



      reply	other threads:[~2017-09-30  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  6:21 [Patch] FDF Spec: Per PI 1.6 to support FV extended header contain FV used size Yonghong Zhu
2017-09-30  5:23 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E1671C6@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