From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]: PCI ROM support.
Date: Thu, 03 Jun 2004 16:11:23 +0200 [thread overview]
Message-ID: <40BF318B.6020109@bellard.org> (raw)
In-Reply-To: <1086134382.21903.84.camel@sherbert>
Hi,
I commited a variant of your patch - try it. I also added support for
opaque data on all memory I/Os.
Fabrice.
Gianni Tedesco wrote:
> Attached is a preliminary patch which adds support for ROM resources to
> the PCI subsystem as a 7th resource. It's fairly self explanatory, but
> for some reason in my guest Linux OS, ROM resources are all sized to 2KB
> (but unassigned and disabled) even if the ROM base address register
> (@0x30) is all zeros... Not sure if it's just the version of lspci I'm
> using...
>
> There is probably an obvious bug that Fabrice can spot ;)
next prev parent reply other threads:[~2004-06-03 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 23:59 [Qemu-devel] [PATCH]: PCI ROM support Gianni Tedesco
2004-06-03 14:11 ` Fabrice Bellard [this message]
2004-06-03 16:06 ` Gianni Tedesco
2004-06-03 16:43 ` Fabrice Bellard
2004-06-03 17:02 ` Gianni Tedesco
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=40BF318B.6020109@bellard.org \
--to=fabrice@bellard.org \
--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).