From: gshan <gshan@alcatel-lucent.com>
To: linux-next@vger.kernel.org
Subject: PCI device memory bars issue
Date: Thu, 26 Jun 2008 10:19:44 +0800 [thread overview]
Message-ID: <4862FCC0.3050501@alcatel-lucent.com> (raw)
There has one MV64460 on my board, which contains 2 PCI buses: PCI0 and
PCI1.
PCI0 contains a transparent bridge. A PCI device locates behind the
transparent
bridge. The PCI device has 2 memory bars. When I read on memory bar0, it
returns
correct data. However, 0xffffffff returns from memory bar1.
I dump config space of the PCI device and find everything seems ok.
PCI_VENDOR_ID: 0x000010ee
PCI_DEVICE_ID: 0x00000300
PCI_COMMAND: 0x00000086
PCI_STATUS: 0x00000a00
PCI_CLASS_REVISION: 0x0b400000
PCI_CACHE_LINE_SIZE: 0x0000ff00
PCI_BASE_ADDRESS_0: 0x80800008
PCI_SPACE_SIZE_0: 0xfffff008
PCI_BASE_ADDRESS_1: 0x80801008
PCI_SPACE_SIZE_1: 0xfffff008
PCI_BASE_ADDRESS_2: 0x00000000
PCI_SPACE_SIZE_2: 0x00000000
PCI_BASE_ADDRESS_3: 0x00000000
PCI_SPACE_SIZE_3: 0x00000000
PCI_BASE_ADDRESS_4: 0x00000000
PCI_SPACE_SIZE_4: 0x00000000
PCI_BASE_ADDRESS_5: 0x00000000
PCI_SPACE_SIZE_5: 0x00000000
Thanks in advance for any suggestions.
reply other threads:[~2008-06-26 2:19 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=4862FCC0.3050501@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=linux-next@vger.kernel.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).