From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mj0by-0002po-KK for qemu-devel@nongnu.org; Wed, 02 Sep 2009 20:55:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mj0bt-0002pc-6x for qemu-devel@nongnu.org; Wed, 02 Sep 2009 20:55:37 -0400 Received: from [199.232.76.173] (port=36756 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mj0bt-0002pZ-0z for qemu-devel@nongnu.org; Wed, 02 Sep 2009 20:55:33 -0400 Received: from mx09.roch.ny.frontiernet.net ([66.133.183.226]:51177) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mj0bs-0007IO-Ki for qemu-devel@nongnu.org; Wed, 02 Sep 2009 20:55:32 -0400 Received: from fys (70-100-44-137.br1.sho.az.frontiernet.net [70.100.44.137]) by relay01.roch.ny.frontiernet.net (Postfix) with ESMTPA id 9EFC05FF54 for ; Thu, 3 Sep 2009 00:55:31 +0000 (UTC) Message-ID: <000501ca2c31$59671d30$01fea8c0@fys> From: "Benjamin David Lunt" Date: Wed, 2 Sep 2009 17:56:14 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] pci bug Reply-To: Benjamin David Lunt List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, Sorry to keep posting to the list like this, please forgive me. However, I may have found a bug with the PCI code too. (please correct me if I am wrong) If I do the following: #define PCI_ADDR 0x0CF8 #define PCI_DATA 0x0CFC // bus 0, dev 0, func 0, addr 0 outpd(PCI_ADDR, 0x80000000); // read in the dword at addr 0 offset 0 // and // read in the word at addr 0 offset 2 // and the word at addr 1 offset 0 printf("0x%08X 0x%08X", inpd(PCI_DATA), inpd(PCI_DATA+2)); Qemu (0.10.6 Windows build) returns 0x12378086 0xFFFFFFFF It seems that if I read from any offset other than PCI_DATA, QEMU is returning 0xFFFFFFFF. Shouldn't PCI_DATA+1, PCI_DATA+2, and PCI_DATA+3 all be registered to the PCI emulation? Again, hope this isn't a bother. However, would someone please check this for me and verify that it is a bug. I can't image it failing if Linux works fine. It may be the Windows build only, I don't know. Thanks, Ben