From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=48304 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P7ucv-0002IO-Um for qemu-devel@nongnu.org; Mon, 18 Oct 2010 14:40:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P7ucu-0003HS-Ts for qemu-devel@nongnu.org; Mon, 18 Oct 2010 14:40:05 -0400 Received: from mail-qy0-f173.google.com ([209.85.216.173]:39250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P7ucs-0003Gu-W3 for qemu-devel@nongnu.org; Mon, 18 Oct 2010 14:40:04 -0400 Received: by qyk36 with SMTP id 36so4189309qyk.4 for ; Mon, 18 Oct 2010 11:40:02 -0700 (PDT) Message-ID: <4CBC946A.1010100@codemonkey.ws> Date: Mon, 18 Oct 2010 13:39:38 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/2] pci: Automatically patch PCI device id in PCI ROM References: <1287175867-7757-1-git-send-email-weil@mail.berlios.de> <4CB8C20A.70706@codemonkey.ws> <4CBC1CD3.1040904@redhat.com> In-Reply-To: <4CBC1CD3.1040904@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: Kevin Wolf , "Michael S. Tsirkin" , seabios@seabios.org, QEMU Developers , Markus Armbruster On 10/18/2010 05:09 AM, Gerd Hoffmann wrote: > On 10/15/10 23:05, Anthony Liguori wrote: >> On 10/15/2010 03:51 PM, Stefan Weil wrote: >>> PCI device with different device ids sometimes share >>> the same rom code. Only the device id and the checksum >>> differ in a boot rom for such devices. >> >> BTW, SeaBIOS doesn't reject ROMs when they're loaded via rombar, only >> when they're loaded via romfile. > > SeaBIOS rejects them when loaded from the rom bar and doesn't reject > them when loaded via fw_cfg. What I meant was, rombar=0 in qdev. Sometimes my fingers don't work the same way my brain does :-) > Using the rom bar is the prefered way though, fw_cfg is only there for > compatibility with older versions. > >> Maybe it's better to use fw_cfg to explicitly tell SeaBIOS to ignore the >> PCI device id in the rom header for a certain device? > > Patching the rom is fine IMHO. Why create + use a separate > communication path when we can use a much simpler approach? How does this interact with PCI device passthrough? We clearly can't patch in that case whereas if we had a hint to SeaBIOS, it would still work. Regards, Anthony Liguori > cheers, > Gerd >