From: "Wu, Hao A" <hao.a.wu@intel.com>
To: devel@edk2.groups.io
Cc: Hao A Wu <hao.a.wu@intel.com>, Ray Ni <ray.ni@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v3 0/4] Ovmf: Drop IntelFramework[Module]Pkg dependency
Date: Fri, 14 Jun 2019 13:18:50 +0800 [thread overview]
Message-ID: <20190614051854.8856-1-hao.a.wu@intel.com> (raw)
The series is also available at:
https://github.com/hwu25/edk2/tree/ovmf_drop_framework_v3
V3 changes:
* Abandon the changes made in V2. Since the duplication of required CSM
modules by OvmfPkg is done (rather than drop the CSM support on OVMF).
* Use the symbolic GUID already defined in ShellPkg to refer the UEFI
Shell app, instead of using the PCD
gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile.
V2 history:
* Update to module OvmfPkg/Csm/CsmSupportLib/CsmSupportLib.inf has been
dropped, since the module is proposed to be removed in another series:
https://edk2.groups.io/g/devel/message/42142
* Copy LegacyBios protocol definitions from IntelFrameworkPkg, since
OvmfPkg/IncompatiblePciDeviceSupportDxe/IncompatiblePciDeviceSupport.inf
has a dependency on it. This was not done in V1 series since such copy
was previous covered by another series to duplicate the required CSM
modules into OvmfPkg. (Now this series has been dropped.)
V1 history:
The series will drop the IntelFramework[Module]Pkg dependency for below
modules within OvmfPkg:
OvmfPkg/PlatformPei/PlatformPei.inf
OvmfPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf
OvmfPkg/IncompatiblePciDeviceSupportDxe/IncompatiblePciDeviceSupport.inf
OvmfPkg/Csm/CsmSupportLib/CsmSupportLib.inf
Verification done for the series:
* Build pass for OvmfPkg;
* Boot to shell with the built images.
Cc: Ray Ni <ray.ni@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Hao A Wu (6):
OvmfPkg/PlatformPei: Remove redundant reference of framework pkg DEC
OvmfPkg/IncompatiblePciDeviceSupportDxe: Drop framework pkg dependency
OvmfPkg/Csm/CsmSupportLib: Drop IntelFrameworkPkg dependency
OvmfPkg: Refer to Shell app via its declared GUID
OvmfPkg/OvmfPkgIa32.dsc | 2 --
OvmfPkg/OvmfPkgIa32X64.dsc | 2 --
OvmfPkg/OvmfPkgX64.dsc | 2 --
OvmfPkg/Csm/CsmSupportLib/CsmSupportLib.inf | 3 +--
OvmfPkg/IncompatiblePciDeviceSupportDxe/IncompatiblePciDeviceSupport.inf | 1 -
OvmfPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf | 6 +++---
OvmfPkg/PlatformPei/PlatformPei.inf | 3 +--
OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c | 4 ++--
8 files changed, 7 insertions(+), 16 deletions(-)
--
2.12.0.windows.1
next reply other threads:[~2019-06-14 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 5:18 Wu, Hao A [this message]
2019-06-14 5:18 ` [PATCH v3 1/4] OvmfPkg/PlatformPei: Remove redundant reference of framework pkg DEC Wu, Hao A
2019-06-14 5:18 ` [PATCH v3 2/4] OvmfPkg/IncompatiblePciDeviceSupportDxe: Drop framework pkg dependency Wu, Hao A
2019-06-14 5:18 ` [PATCH v3 3/4] OvmfPkg/Csm/CsmSupportLib: Drop IntelFrameworkPkg dependency Wu, Hao A
2019-06-14 5:18 ` [PATCH v3 4/4] OvmfPkg: Refer to Shell app via its declared GUID Wu, Hao A
2019-06-14 20:32 ` [edk2-devel] " Laszlo Ersek
2019-06-17 1:28 ` Wu, Hao A
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=20190614051854.8856-1-hao.a.wu@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