From: Robert Hancock <hancockr@shaw.ca>
To: mcharon@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to access pci memory from driver?
Date: Thu, 22 Jun 2006 19:19:52 -0600 [thread overview]
Message-ID: <449B41B8.8040009@shaw.ca> (raw)
In-Reply-To: <1150930994.956075.281770@c74g2000cwc.googlegroups.com>
mcharon@gmail.com wrote:
> hi steve,
> that's another thing i forgot to mention. lspci doesn't show anything.
> so it seems that there's no pci device. but the fact that cat
> /proc/iomem shows
> 0x60000000-0x67ffffff : PCI1 host bridge, does this mean that the my
> device which is supposed to be at 0x60040000 is mapped to I/O space??
> the lease significant bit of bar0 is indeed 0.
>
> the linux is running on ppc platform. we had to modify the u-boot in
> order to load linux on our system. so i am not sure if we have
> performed the necessary steps to be able to map our pci device.
>
> for one thing, we are not registering any of our pci devices when uboot
> loads
> linux. we are going to use our driver to read and write to the pci
> device.
> can we still map to the device eventhough it is not registered?
I don't know PPC, but if your device doesn't even show up in lspci then
you have bigger problems than your driver, either with the device, the
machine hardware or the kernel's PCI detection.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
parent reply other threads:[~2006-06-23 1:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1150930994.956075.281770@c74g2000cwc.googlegroups.com>]
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=449B41B8.8040009@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mcharon@gmail.com \
/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