From: Rebecca Cran <rebecca@bluestop.org>
To: "Shah, Tapan" <tapandshah@hpe.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: EFI_FIRMWARE_IMAGE_DESCRIPTOR v1/v2/v3: MdePkg and ShellPkg
Date: Thu, 16 Feb 2017 16:16:36 -0700 [thread overview]
Message-ID: <7bd3b2ba-4781-fd3f-6d45-b18ec66b4ee7@bluestop.org> (raw)
In-Reply-To: <CS1PR84MB0024BE62FFA81148070816A7D45A0@CS1PR84MB0024.NAMPRD84.PROD.OUTLOOK.COM>
On 2/16/2017 3:59 PM, Shah, Tapan wrote:
> UEFI Spec does not have old FMP image descriptor structures V1 and V2 defined.
>
> MdePkg only follows the spec, so it contains the latest version # 3. But there are still drivers using old V1, V2 revisions and Shell 'dh' command needs to support decoding all revisions and needs to remain in ShellPkg.
Ah, okay - thanks. I was thinking that drivers might still like to
support older systems that still run UEFI 2.3, 2.4 etc. and so would
need to access the older structures.
--
Rebecca
prev parent reply other threads:[~2017-02-16 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:47 EFI_FIRMWARE_IMAGE_DESCRIPTOR v1/v2/v3: MdePkg and ShellPkg Rebecca Cran
2017-02-16 22:58 ` Yao, Jiewen
2017-02-16 22:59 ` Shah, Tapan
2017-02-16 23:12 ` Yao, Jiewen
2017-02-17 15:42 ` Shah, Tapan
2017-02-17 16:03 ` Carsey, Jaben
2017-02-17 16:46 ` Shah, Tapan
2017-02-16 23:16 ` Rebecca Cran [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=7bd3b2ba-4781-fd3f-6d45-b18ec66b4ee7@bluestop.org \
--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