Hi, > It's an interesting question - is it better to compile a vgabios for a > specific hardware or to make a vgabios compatible with several > different pieces of hardware. I don't know what the right answer is.
Alot of stuff seems to be shared, the size doesn't go up much: -rw-rw-r--. 1 kraxel kraxel 35328 Jan 26 10:50 vgabios-bochs.bin -rw-rw-r--. 1 kraxel kraxel 36352 Jan 26 10:50 vgabios-cirrus.bin -rw-rw-r--. 1 kraxel kraxel 38400 Jan 26 10:50 vgabios-both.bin > There's some simplicity for qemu/kvm in that only one blob is needed. > BTW, the PCI spec does allow (with some magic to the pci struct) for > multiple roms to be concatenated together to obtain a single blob for > different hardware. That are multiple, independant roms which are chained together I guess? So the seabios could walk the list, then grab the one which matches the pci id of the device? > I have some changes in my repo pending for vgahw.h (to support the > remaining cirrus vbe calls). I'd want to get those pushed before > changing the way vgahw.h works. Sure. cheers, Gerd _______________________________________________ SeaBIOS mailing list [email protected] http://www.seabios.org/mailman/listinfo/seabios
