Re: [SeaBIOS] Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?)
On Tue, Dec 15, 2009 at 10:24:29PM +0100, Sebastian Herbszt wrote:
Keep loading custom roms (e.g. from -option-rom) with rom_add_file starting at 0xc8000. Modify SeaBIOS to scan the memory range for pre-deployed option roms before deploying PCI roms. SeaBIOS will find the last pre-deployed rom and have a starting address for deploying PCI roms. This will keep ISA option roms working.
Unfortunately, if the SeaBIOS post entry gets called again (eg, on ctrl+alt+del), it wont know which roms were originally present, and which roms were deployed by SeaBIOS on the first boot.
-Kevin
On 12/16/09 05:29, Kevin O'Connor wrote:
On Tue, Dec 15, 2009 at 10:24:29PM +0100, Sebastian Herbszt wrote:
Keep loading custom roms (e.g. from -option-rom) with rom_add_file starting at 0xc8000. Modify SeaBIOS to scan the memory range for pre-deployed option roms before deploying PCI roms. SeaBIOS will find the last pre-deployed rom and have a starting address for deploying PCI roms. This will keep ISA option roms working.
Unfortunately, if the SeaBIOS post entry gets called again (eg, on ctrl+alt+del), it wont know which roms were originally present, and which roms were deployed by SeaBIOS on the first boot.
option roms loaded by seabios via pci seem to care only about the pci device they where loaded from. So this optionrom <=> pcidevice relationship must be stored somewhere. Can SeaBIOS use that to figure which option roms where loaded by seabios itself?
cheers, Gerd
-
Gerd Hoffmann -
Kevin O'Connor