On Wed, Sep 25, 2013 at 12:24:18PM +0200, Gerd Hoffmann wrote:
Hi,
Imagine you have QEMU 1.7. You want to update bios, so you pull latest source. Of course roms/config.seabios-128k does not know which flags to set :(
Hmm? That is the whole point of the file, to carry the (non-default) config options ...
Latest qemu should have a up-to-date info for latest seabios release. When updating seabios to not-yet released master you better know what you are doing, I don't think there is a need to make that bullet-proof.
cheers, Gerd
Simply put - it's in a separate tree so it will be foreever out of sync.
Example: you want to try and reproduce a bug with latest seabios. You build it with options from which qemu? The one you will be testing on right? Wrong - it might not work.
This just does not work - it's not reasonable for QEMU to carry guest knowledge around. Instead guests should go "I want to work on that QEMU". And QEMU will supply specific interfaces.
config options is also not an interface we can support. So there will be pain when we rename some option. A simple "small bios/large bios" is an interface we should have no trouble supporting for a long time, so it will be possible for qemu to carry that around.