From: "Sandeep Dhanvada" <sandeep.dhanvada@xilinx.com>
To: <devel@edk2.groups.io>
Cc: <sandeep.dhanvada@xilinx.com>
Subject: [PATCH 0/2] OvmfPkg: FMP Capsule Update Modifications.
Date: Mon, 9 Nov 2020 16:33:02 +0530 [thread overview]
Message-ID: <cover.1604918017.git.sandeep.dhanvada@xilinx.com> (raw)
This patch enables FMP Capsule upgrade of firmware on PCI add on
cards with PCI Passthrough enabled in OVMF environment by enabling
DxeCapsuleLibFmp and EsrtFMP modules.
DxeCapsuleLibFmp/DxeCapsuleLib.c has modifications to connect to
all controllers after capsule update is executed. This enables FMP
SetImage() to be executed through UpdateCapsule(). without this
change, connect command has to be issued manually from UEFI Shell
for the FMP SetImage() to execute.
FMP capsule update is validated using CapsuleApp.efi, with -E option
dumping the ESRT Table fetched from FMP producer on PCI UEFI driver.
capsule update is validated using capsulefile generated using
BaseTools/Source/Python/Capsule/GenerateCapsule.py.
Sandeep Dhanvada (2):
MdeModulePkg: Capsule upgrade fixes.
OvmfPkg: Add EsrtFmpDxe in OVMF X64 Builds.
.../Library/DxeCapsuleLibFmp/DxeCapsuleLib.c | 43 ++++++++++++++++++++++
OvmfPkg/OvmfPkgX64.dsc | 4 +-
OvmfPkg/OvmfPkgX64.fdf | 1 +
3 files changed, 47 insertions(+), 1 deletion(-)
--
2.1.1
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
next reply other threads:[~2020-11-09 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 11:03 Sandeep Dhanvada [this message]
2020-11-09 11:03 ` [PATCH 1/2] MdeModulePkg: Capsule upgrade fixes Sandeep Dhanvada
2020-11-09 11:03 ` [PATCH 2/2] OvmfPkg: Add EsrtFmpDxe in OVMF X64 Builds Sandeep Dhanvada
2020-11-10 21:17 ` [edk2-devel] " Laszlo Ersek
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=cover.1604918017.git.sandeep.dhanvada@xilinx.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