From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FbiPY-0000DW-PE
	for qemu-devel@nongnu.org; Thu, 04 May 2006 14:18:48 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FbiPX-0000DB-BW
	for qemu-devel@nongnu.org; Thu, 04 May 2006 14:18:48 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FbiPX-0000D8-6W
	for qemu-devel@nongnu.org; Thu, 04 May 2006 14:18:47 -0400
Received: from [84.96.92.56] (helo=smTp.neuf.fr)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FbiQC-000529-3Z
	for qemu-devel@nongnu.org; Thu, 04 May 2006 14:19:28 -0400
Received: from [84.102.211.43] by sp604003mt.gpm.neuf.ld
	(Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006))
	with ESMTP id <0IYR006E36TLH6O0@sp604003mt.gpm.neuf.ld> for
	qemu-devel@nongnu.org; Thu, 04 May 2006 20:17:45 +0200 (CEST)
Date: Thu, 04 May 2006 20:17:04 +0200
From: Fabrice Bellard <fabrice@bellard.org>
Subject: Re: [Qemu-devel] Unknown PCI Bridge
In-reply-to: <445A0480.7010001@cnpbagwell.com>
Message-id: <445A4520.9040300@bellard.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <445A0480.7010001@cnpbagwell.com>
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

Chris Bagwell wrote:
> Hi all,
> 
> I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).  
> Last time I upgraded was about 1 week ago.
> 
> When I ran this version with a win98 guest, windows detected a new 
> device called "PCI Bridge".  It was unable to find a driver for this on 
> the win98 CD and placed it as not working in the "other devices" section 
> of device manager.
> 
> Doesn't seem to harm anything.  I was guessing it had something to do 
> with the acpi patches but haven't verified.  Any ideas?

Yes, ACPI adds a new PCI device so it is normal. I am interested by any 
regression found using the current CVS with ACPI...

Fabrice.