From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKdBh-0003N9-Kv for qemu-devel@nongnu.org; Tue, 15 Dec 2009 14:36:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKdBc-0003Io-SI for qemu-devel@nongnu.org; Tue, 15 Dec 2009 14:36:01 -0500 Received: from [199.232.76.173] (port=55686 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKdBc-0003Il-Md for qemu-devel@nongnu.org; Tue, 15 Dec 2009 14:35:56 -0500 Received: from mail-yw0-f171.google.com ([209.85.211.171]:44494) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKdBc-0000Rt-CI for qemu-devel@nongnu.org; Tue, 15 Dec 2009 14:35:56 -0500 Received: by ywh1 with SMTP id 1so218158ywh.18 for ; Tue, 15 Dec 2009 11:35:55 -0800 (PST) Message-ID: <4B27E518.7060300@codemonkey.ws> Date: Tue, 15 Dec 2009 13:35:52 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) References: <4B264AF1.6060802@codemonkey.ws> <7FB8DD1225E54176BCAF5523B6AEA89B@FSCPC> <4B26931E.4000101@codemonkey.ws> <20091214194210.GB6150@redhat.com> <4B269933.3010906@codemonkey.ws> <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> <4B276197.1080606@redhat.com> In-Reply-To: <4B276197.1080606@redhat.com> 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: Gerd Hoffmann Cc: "Michael S. Tsirkin" , glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Sebastian Herbszt Gerd Hoffmann wrote: > -kernel didn't work on a quick test. Thinking about how to fix this, we have two options. The first would be to use the support in SeaBIOS for static roms but that would limit us to two user supplied option roms (including kernel/multiboot/extboot). We could extend this to more than two roms but I think that's generally ugly. Alternatively, we could introduce a special rom-only PCI device. Besides getting support for a much greater number of option roms, it also gives us a much nicer way to integrate multiboot/linux boot support via qdev (instead of the ugly machine hack we have now). We could make them multifunction devices so that we don't unnecessarily burn PCI slots to support roms. Regards, Anthony Liguori > cheers, > Gerd