From: "Benjamin David Lunt" <fys@frontiernet.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] pci bug
Date: Wed, 2 Sep 2009 17:56:14 -0700 [thread overview]
Message-ID: <000501ca2c31$59671d30$01fea8c0@fys> (raw)
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
reply other threads:[~2009-09-03 0:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000501ca2c31$59671d30$01fea8c0@fys' \
--to=fys@frontiernet.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).