On Fri, 2013-02-08 at 04:44 +0000, Li, Elvin wrote: > > I guess this virtual disk comes from a virtual disk > controller. Now you only fill an entry in BBS table to show legacy > boot options, I am unclear that how you enable real legacy boot for > this virtual disk finally? The bbs entry you filled does not include > the BCV/BEV address and is more like a dummy entry.
Which is exactly like the entries for IDE devices. If you care, take a look at the way it's handled in the SeaBIOS CSM, with csm_bootprio_pci() funding the appropriate entry in the table and ordering the boot option accordingly. Surely this is how we're *supposed* to support block devices for which we also have a native EFI driver? Unless we're supposed to somehow have them simultaneously driven by the legacy option rom *and* the EFI driver, early in the startup process before we've decided what to boot from? -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
