On Mon, 2013-11-11 at 16:58 +0100, Laszlo Ersek wrote: > I think the SeaBIOS binary in Fedora 19 is *not* buggy in this regard. I > assume though that SeaBIOS and/or SeaVGABIOS in Fedora 19 are not built > with the correct config options for CSM.
SeaVGABIOS shouldn't need to be built for CSM. It should just work, either will. > I use the following config options when building upstream SeaBIOS and > SeaVGABIOS for CSM (note that this is two separate builds): > > SeaBIOS: > > cat >.config <<-EOT > CONFIG_CSM=y > CONFIG_QEMU_HARDWARE=y > CONFIG_PERMIT_UNALIGNED_PCIROM=y That one should be irrelevant. It's OVMF which will decline to use broken ROMs, and I don't think this setting even affects any code which is included in the CSM build of SeaBIOS. > CONFIG_DEBUG_LEVEL=20 > EOT > yes "" | make oldconfig > make -j2 out/bios.bin > mv -- out/bios.bin "$SIDE_COPY"/Csm16.bin > > > SeaVGABIOS: > > make distclean > cat >.config <<-EOT > CONFIG_QEMU=y > CONFIG_BUILD_VGABIOS=y > CONFIG_VGA_CIRRUS=y > CONFIG_VGA_PCI=y > CONFIG_DEBUG_LEVEL=20 > EOT > yes "" | make oldconfig > make -j2 out/vgabios.bin > cat out/vgabios.bin >| "$INST"/vgabios-cirrus.csm.bin That (from git master) builds me a working SeaVGABIOS. Thanks. I'll see if I can work out what's wrong with the Fedora 19 one. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
