On Thu, Mar 21, 2013 at 01:49:36PM +0100, Gerd Hoffmann wrote:
Hi,
How about we don't bother to determine this at runtime at all?
Because it will be a PITA for testers + developers to figure the correct .config switches of the day during the transition phase?
Why is it a PITA? Are you developing QEMU? Just use the makefile from roms/config.seabios Are you using QEMU binary? Just use the defaults.
SeaBIOS binaries are running on a wide range of qemu versions today. Changing that is a big deal.
Chaqnging what? Legacy QEMU will keep working if you build in ACPI tables.
People are not used to it, and even when writing it to the README people will stumble over it. It also is pretty inconvenient in a number of cases.
Could you give me one example?
I don't get it. If you are working on both QEMU and seabios, you better build seabios in the way that qemu build process uses. Anything else is just wrong on so many levels...
For starters the usual way to package seabios and qemu in distros is to have separate packages ...
cheers, Gerd
Which ones? That's just crazy. Fedora packages them together: qemu-system-x86-1.2.2-6.fc18.i686 bios is a firmware flashed on the motherboard. You want to change motherboard but use the same firmware?