From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BXluX-00034N-T0 for qemu-devel@nongnu.org; Tue, 08 Jun 2004 15:05:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BXluW-00034A-86 for qemu-devel@nongnu.org; Tue, 08 Jun 2004 15:05:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BXluW-000347-4t for qemu-devel@nongnu.org; Tue, 08 Jun 2004 15:05:24 -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 1BXltp-0005o3-F1 for qemu-devel@nongnu.org; Tue, 08 Jun 2004 15:04:41 -0400 Subject: Re: [Qemu-devel] ISA PnP support From: Gianni Tedesco In-Reply-To: <40C0ADD0.4090808@bellard.org> References: <1086365733.6650.44.camel@pcgem.rdg.cyberkinetica.com> <40C0A482.8010503@bellard.org> <1086368692.21903.150.camel@sherbert> <40C0ADD0.4090808@bellard.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-IfVQKfWBTxMscE1zvEh/" Date: Tue, 08 Jun 2004 19:56:59 +0100 Message-Id: <1086721019.21922.226.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 --=-IfVQKfWBTxMscE1zvEh/ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-06-04 at 19:13 +0200, Fabrice Bellard wrote: > Gianni Tedesco wrote: > > On Fri, 2004-06-04 at 18:34 +0200, Fabrice Bellard wrote: > >=20 > >>I am not really interested by ISA PnP as PCI will be the default config= =20 > >>as soon as it works for NT. But I can still look at the patch. > >=20 > >=20 > > I've bumped in to this myself but not had time to look at it. What is > > the problem with NT/2k? Or is it as yet undiagnosed? >=20 > I did not try to find it yet (not reached in my TODO list). Activating=20 > the PCI traces while NT boots should give a lot of valuable information. Well I can verify that the bug installing 2k (pausing half way on detecting hardware) has gone with the latest CVS version. Although the bluescreen when enabling PCI on a vm installed without PCI persists. I don't think we can fix this one as the problem is missing boot device. If -pci is default in future then there should be no problem I think. --=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 --=-IfVQKfWBTxMscE1zvEh/ 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) iD8DBQBAxgv6kbV2aYZGvn0RAiwmAJ9/Avl2mVSLolPlyO6morwe3iQfDwCfVIOe +0WDfq+o6tdlHxAtrQh7/tg= =Rp/P -----END PGP SIGNATURE----- --=-IfVQKfWBTxMscE1zvEh/--