> -----Original Message----- > From: David Woodhouse [mailto:dw...@infradead.org] > Sent: Wednesday, June 12, 2019 8:08 PM > To: devel@edk2.groups.io; ler...@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. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#42325): https://edk2.groups.io/g/devel/message/42325 Mute This Topic: https://groups.io/mt/32011839/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
