From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKsa4-0005BT-Hc for qemu-devel@nongnu.org; Wed, 16 Dec 2009 07:02:12 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKsZz-000598-ID for qemu-devel@nongnu.org; Wed, 16 Dec 2009 07:02:11 -0500 Received: from [199.232.76.173] (port=49811 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKsZz-00058g-2K for qemu-devel@nongnu.org; Wed, 16 Dec 2009 07:02:07 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56879) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKsZy-0008HX-Lf for qemu-devel@nongnu.org; Wed, 16 Dec 2009 07:02:06 -0500 Message-ID: <4B28CC31.4070308@redhat.com> Date: Wed, 16 Dec 2009 13:01:53 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) References: <20091214202019.GF6150@redhat.com> <4B26A0DE.5000304@redhat.com> <20091214203428.GI6150@redhat.com> <20091214203603.GJ6150@redhat.com> <4B26A3B2.2030006@codemonkey.ws> <20091214205141.GC6398@redhat.com> <4B26F678.4010603@codemonkey.ws> <4B27541F.9020603@redhat.com> <4B278C34.6080401@codemonkey.ws> <20091216042920.GB12410@morn.localdomain> In-Reply-To: <20091216042920.GB12410@morn.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: "Michael S. Tsirkin" , glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf , Sebastian Herbszt 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