From: "Wu, Hao A" <hao.a.wu@intel.com>
To: David Woodhouse <dwmw2@infradead.org>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Phillips, D Scott" <d.scott.phillips@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency
Date: Thu, 13 Jun 2019 05:47:36 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8F001C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <5df502494d27d043490b892c68ec6816d9ca9def.camel@infradead.org>
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Wednesday, June 12, 2019 8:08 PM
> To: devel@edk2.groups.io; lersek@redhat.com; Wu, Hao A; Ni, Ray; Justen,
> Jordan L
> Cc: Ard Biesheuvel; Phillips, D Scott
> Subject: Re: [edk2-devel] [PATCH v2 0/6] Ovmf: Drop
> IntelFramework[Module]Pkg dependency
>
> On Wed, 2019-06-12 at 13:52 +0200, Laszlo Ersek wrote:
> >
> > I don't think it's on Hao to determine an (edk2 base commit, SeaBIOS
> > base commit) pair from the past at which the CSM functionality worked
> > "flawlessly".
>
> Absolutely!
>
> I was only suggesting that Hao should make sure it doesn't get worse.
The test I performed is to verify booting legacy Windows 7 on a real
platform consuming the CSM components under IntelFrameworkModulePkg.
But I do not have much idea on what should I do to verify the duplicated
components under OvmfPkg when proposing this series. Is there any
suggestion here? I tried (but not with great effort) on building a SeaBIOS
binary, but failed to do so due to limited document on how to get it done.
(Maybe an update to OvmfPkg/Csm/Csm16/ReadMe.txt?)
Best Regards,
Hao Wu
>
> When I first did it, I had various versions of Windows and Linux and
> *BSD working correctly. I'm still working when time allows on working
> out how to get back to that state.
>
> But right now it does at least show that it's getting correctly into
> SeaBIOS and handling a bunch of requests before it crashes. As long as
> it still gets that far after Hao's patches, that's fine.
next prev parent reply other threads:[~2019-06-13 5:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 1:43 [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 1/6] OvmfPkg/PlatformPei: Remove redundant reference of framework pkg DEC Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 2/6] OvmfPkg/OvmfPkg.dec: Add PcdShellFile in OVMF DEC file Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 3/6] OvmfPkg/PlatformBootManagerLib: Use PcdShellFile defined in OvmfPkg Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 4/6] OvmfPkg/DSC: Remove the consume of PcdShellFile in framework package Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 5/6] OvmfPkg: Copy LegacyBios protocol definitions from IntelFrameworkPkg Wu, Hao A
2019-06-11 1:43 ` [PATCH v2 6/6] OvmfPkg/IncompatiblePciDeviceSupportDxe: Drop framework pkg dependency Wu, Hao A
2019-06-11 6:49 ` [PATCH v2 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency Ard Biesheuvel
2019-06-11 7:35 ` Jordan Justen
2019-06-11 7:37 ` David Woodhouse
2019-06-11 7:49 ` Wu, Hao A
2019-06-11 8:01 ` David Woodhouse
2019-06-11 8:06 ` Wu, Hao A
2019-06-12 1:19 ` Wu, Hao A
2019-06-12 2:04 ` Ni, Ray
2019-06-12 2:13 ` Wu, Hao A
2019-06-12 7:58 ` Laszlo Ersek
2019-06-12 8:03 ` David Woodhouse
2019-06-12 11:52 ` Laszlo Ersek
2019-06-12 12:08 ` [edk2-devel] " David Woodhouse
2019-06-13 5:47 ` Wu, Hao A [this message]
2019-06-12 15:15 ` David Woodhouse
2019-06-12 16:28 ` Laszlo Ersek
2019-06-12 9:50 ` [edk2-devel] " Ni, Ray
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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8F001C@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