qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]: PCI ROM support.
Date: Thu, 03 Jun 2004 17:06:59 +0100	[thread overview]
Message-ID: <1086278819.21903.108.camel@sherbert> (raw)
In-Reply-To: <40BF318B.6020109@bellard.org>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Thu, 2004-06-03 at 16:11 +0200, Fabrice Bellard wrote:
> Hi,
> 
> I commited a variant of your patch - try it. I also added support for 
> opaque data on all memory I/Os.

Thanks Fabrice, that does everything I need now and the opaque data on
memory I/Os is very neat. I shall be ready to post a more complete
version of my pciproxy patch soon. Just one minor niggle regarding the
ROM code.

I notice you preserve the ROM enable bit, thats useful :)

However this still isn't solving my wierd problem with lspci on Linux
showing all devices as having a 2KB unassigned, disabled ROM chip where
normally it wouldnt print anything. In the config space the ROM bar is
0x00000000...

How are the BARs sized, by writing 0xffffffff over them then re-reading
once? It doesn't mention anything in the i440FX manual... Just waffles
on about the PMC extended register space.

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-03 16:08 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
2004-06-03 16:06   ` Gianni Tedesco [this message]
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=1086278819.21903.108.camel@sherbert \
    --to=gianni@scaramanga.co.uk \
    --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).