From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BVulc-0000cp-E1 for qemu-devel@nongnu.org; Thu, 03 Jun 2004 12:08:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BVula-0000cd-P8 for qemu-devel@nongnu.org; Thu, 03 Jun 2004 12:08:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVula-0000ca-Kv for qemu-devel@nongnu.org; Thu, 03 Jun 2004 12:08:30 -0400 Received: from [213.146.130.142] (helo=trantor.org.uk) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BVul3-0001Ep-8m for qemu-devel@nongnu.org; Thu, 03 Jun 2004 12:07:58 -0400 Subject: Re: [Qemu-devel] [PATCH]: PCI ROM support. From: Gianni Tedesco In-Reply-To: <40BF318B.6020109@bellard.org> References: <1086134382.21903.84.camel@sherbert> <40BF318B.6020109@bellard.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-z+krtrV/jTd1B025X+sR" Date: Thu, 03 Jun 2004 17:06:59 +0100 Message-Id: <1086278819.21903.108.camel@sherbert> Mime-Version: 1.0 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --=-z+krtrV/jTd1B025X+sR Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-06-03 at 16:11 +0200, Fabrice Bellard wrote: > Hi, >=20 > I commited a variant of your patch - try it. I also added support for=20 > 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. --=20 // 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 --=-z+krtrV/jTd1B025X+sR Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAv0yikbV2aYZGvn0RAk9zAJ9Z6uSZX6N7qB3Gv4PV9/cr5c+/VwCdF8Ux BHoDH+1ypUFMoIrp7REpORM= =aWtJ -----END PGP SIGNATURE----- --=-z+krtrV/jTd1B025X+sR--