public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>, Liming Gao <liming.gao@intel.com>
Subject: [PATCH 0/4] Add USED_SIZE FV_EXT_TYPE support
Date: Tue, 28 Nov 2017 17:52:23 +0800	[thread overview]
Message-ID: <1511862747-10220-1-git-send-email-star.zeng@intel.com> (raw)

The USED_SIZE FV_EXT_TYPE is introduced by PI 1.6 spec.

The EFI_FIRMWARE_VOLUME_EXT_ENTRY_USED_SIZE_TYPE can be used to find
out how many EFI_FVB2_ERASE_POLARITY bytes are at the end of the FV.

When the FV gets shadowed into memory you only need to copy the used
bytes into memory and fill the rest of the memory buffer with the
erase value.

Cc: Liming Gao <liming.gao@intel.com>

Star Zeng (4):
  MdePkg PiFirmwareVolume.h: Add USED_SIZE FV_EXT_TYPE definitions
  MdeModulePkg PeiCore: Support USED_SIZE FV_EXT_TYPE
  MdeModulePkg DxeCore: Check FvImage alignment
  MdeModulePkg DxeCore: Support USED_SIZE FV_EXT_TYPE

 MdeModulePkg/Core/Dxe/Dispatcher/Dispatcher.c | 115 +++++++++++++++++++++++---
 MdeModulePkg/Core/Pei/FwVol/FwVol.c           |  91 +++++++++++++++++++-
 MdePkg/Include/Pi/PiFirmwareVolume.h          |  23 +++++-
 3 files changed, 211 insertions(+), 18 deletions(-)

-- 
2.7.0.windows.1



             reply	other threads:[~2017-11-28  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  9:52 Star Zeng [this message]
2017-11-28  9:52 ` [PATCH 1/4] MdePkg PiFirmwareVolume.h: Add USED_SIZE FV_EXT_TYPE definitions Star Zeng
2017-11-28  9:52 ` [PATCH 2/4] MdeModulePkg PeiCore: Support USED_SIZE FV_EXT_TYPE Star Zeng
2017-11-28  9:52 ` [PATCH 3/4] MdeModulePkg DxeCore: Check FvImage alignment Star Zeng
2017-11-28  9:52 ` [PATCH 4/4] MdeModulePkg DxeCore: Support USED_SIZE FV_EXT_TYPE Star Zeng
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29 10:14 [PATCH 0/4] Add USED_SIZE FV_EXT_TYPE support Star Zeng
2017-11-30 11:09 ` 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=1511862747-10220-1-git-send-email-star.zeng@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