From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BVvdS-0007CT-OA
	for qemu-devel@nongnu.org; Thu, 03 Jun 2004 13:04:10 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BVvdS-0007CH-A4
	for qemu-devel@nongnu.org; Thu, 03 Jun 2004 13:04:10 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BVvdS-0007CE-6S
	for qemu-devel@nongnu.org; Thu, 03 Jun 2004 13:04:10 -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 1BVvcz-0006ol-Gn
	for qemu-devel@nongnu.org; Thu, 03 Jun 2004 13:03:41 -0400
Subject: Re: [Qemu-devel] [PATCH]: PCI ROM support.
From: Gianni Tedesco <gianni@scaramanga.co.uk>
In-Reply-To: <40BF554E.80101@bellard.org>
References: <1086134382.21903.84.camel@sherbert>
	<40BF318B.6020109@bellard.org> <1086278819.21903.108.camel@sherbert>
	<40BF554E.80101@bellard.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-OavBQCwS/nXx4aSAbiwo"
Date: Thu, 03 Jun 2004 18:02:45 +0100
Message-Id: <1086282165.21922.121.camel@sherbert>
Mime-Version: 1.0
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


--=-OavBQCwS/nXx4aSAbiwo
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2004-06-03 at 18:43 +0200, Fabrice Bellard wrote:
> Gianni Tedesco wrote:
>=20
> > 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...
>=20
> It is fixed now (an unassigned BAR/ROM should be hardwired to zero).

Cool, yes, that fixes it for me.

Thanks.

--=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

--=-OavBQCwS/nXx4aSAbiwo
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)

iD8DBQBAv1m1kbV2aYZGvn0RAiwLAJ0cMsm7ua2WQ3YAzujnek8JwDwp7QCggkQh
mPi/pKZqf2xFX/Y96cWq3mY=
=DPVB
-----END PGP SIGNATURE-----

--=-OavBQCwS/nXx4aSAbiwo--