qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Paul Brook <paul@codesourcery.com>,
	Hai Shan Bai <haishan.bai@gmail.com>,
	qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH - V3] Port codes from qemu-kvm to support booting from SCSI disk image
Date: Mon, 23 Aug 2010 10:52:56 +0200	[thread overview]
Message-ID: <4C7236E8.2090908@redhat.com> (raw)
In-Reply-To: <20100821142058.GA17139@morn.localdomain>

On 08/21/10 16:20, Kevin O'Connor wrote:
> On Fri, Aug 20, 2010 at 09:39:10AM -0500, Anthony Liguori wrote:
>> On 08/20/2010 09:09 AM, Gerd Hoffmann wrote:
>>> Been there, tried that.  It isn't *that* easy.  The PCI ID in the
>>> option rom header doesn't match the PCI ID of the emulated lsi, so
>>> seabios refuses to load it from the rom bar.
>>
>> Heh, I was wondering why it didn't work unless I put rombar=0 :-)
>>
>> Is this fixable in a reasonable way or does PCI ID in the option rom
>> represent a much newer device that would trigger issues with guest
>> drivers?
>
> The PCI spec requires that the PCI IDs match - this is done so that a
> single rom can store multiple optionroms.
>
> One could place the optionrom in fw_cfg with a "file" name of
> "pciXXXX,YYYY.rom".  SeaBIOS will then deploy that rom for every
> device that has the given vendor/devid.  (It wont require matching PCI
> IDs ids in the rom.)

Yea, this is exactly what "rombar=0" (property for pci devices) does: 
load the rom via fw_cfg instead of using the pci option rom bar ;)

cheers,
   Gerd

      reply	other threads:[~2010-08-23  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  2:06 [Qemu-devel] [PATCH - V3] Port codes from qemu-kvm to support booting from SCSI disk image Hai Shan Bai
2010-08-18  2:20 ` haishan
2010-08-18 15:08 ` Paul Brook
2010-08-18 15:16   ` Alexander Graf
2010-08-18 15:31     ` Haishan Bai
2010-08-18 15:37     ` Gleb Natapov
2010-08-18 16:04       ` Paul Brook
2010-08-19 18:14         ` Blue Swirl
2010-08-18 15:54     ` Paul Brook
2010-08-20  7:44     ` Gerd Hoffmann
2010-08-20 13:42       ` Anthony Liguori
2010-08-20 14:09         ` Gerd Hoffmann
2010-08-20 14:39           ` Anthony Liguori
2010-08-21 14:20             ` Kevin O'Connor
2010-08-23  8:52               ` Gerd Hoffmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C7236E8.2090908@redhat.com \
    --to=kraxel@redhat.com \
    --cc=agraf@suse.de \
    --cc=haishan.bai@gmail.com \
    --cc=kevin@koconnor.net \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).