From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
To: linux-kernel@vger.kernel.org
Subject: PCI resource unavailable on mips
Date: Thu, 13 Dec 2007 09:56:46 -0500 [thread overview]
Message-ID: <1197557806.3370.7.camel@microwave.infinitevideocorporation.com> (raw)
Hi,
I've done a bit of linux driver development on x86 in the past.
Currently I am working on my first ever linux driver for a mips box. I
started by testing the device in an x86 box and got it reasonable stable
and am now testing it in the mips box. There appears to be a major
problem, one unlike I have ever seen before.
My PCI device has three BARS. This can be confirmed by the Technical
documentation and the x86 code. When the pci device is first probed, I
run a loop to printk out the bar information, this is just as a sanity
check. Here is the output on the x86:
Bar0:PHYS=e0000000 LEN=04000000
Bar1:PHYS=efa00000 LEN=00200000
Bar2:PHYS=e8000000 LEN=04000000
but here is the output on the mips:
Bar0:PHYS=20000000 LEN=04000000
Bar1:PHYS=24000000 LEN=00200000
Bar2:PHYS=00000000 LEN=00000000
notice, BAR2 has no valid information on the mips. I tried to run
"pci_enable_device" before printing this information, as suggested by
LDD but it did not help.
Has anyone seen a problem like this before and any idea how I can get
BAR2 a proper address?
If I examine the config space directly there is an address in BAR2's
register, however it isn't in the 0x20000000 range like the other two,
instead it is 0x1c000000. Also if I do a ``cat /proc/iomem'' I correctly
see BAR0 and BAR1 in the output, but not BAR2.
Thanks for any help,
Jon
next reply other threads:[~2007-12-13 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 14:56 Jon Dufresne [this message]
2007-12-14 9:39 ` Ralf Baechle
2007-12-14 18:32 ` Jon Dufresne
2007-12-14 21:12 ` Jon Dufresne
2007-12-16 22:46 ` Ralf Baechle
2007-12-17 15:16 ` Jon Dufresne
2007-12-17 15:47 ` Sergei Shtylyov
2007-12-18 18:11 ` Jon Dufresne
[not found] <fa.vbvzhsk+kDPCopbmajO8EsxAnKE@ifi.uio.no>
2007-12-13 23:38 ` Robert Hancock
2007-12-18 18:40 ` Jon Dufresne
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=1197557806.3370.7.camel@microwave.infinitevideocorporation.com \
--to=jon.dufresne@infinitevideocorporation.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®