From: Felix Radensky <felix@embedded-sol.com>
To: linuxppc-embedded@ozlabs.org
Subject: Accessing PCI-E resources on 460EX
Date: Mon, 03 Nov 2008 23:09:22 +0200 [thread overview]
Message-ID: <490F6882.6050101@embedded-sol.com> (raw)
Hi,
I'm currently struggling with some application
that tries to access PCI-E memory by mmaping
address found in /sys/bus/pci/devices/<device>/resource
mmap() fails with "invalid argument" error, apparently
because on 460EX PCI addresses are 36-bit.
What is the correct way of accessing PCI-E from
userspace on this platform.
Thanks a lot.
Felix Radensky
Embedded Solutions Ltd.
http://www.embedded-sol.com
next reply other threads:[~2008-11-03 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 21:09 Felix Radensky [this message]
2008-11-03 21:31 ` Accessing PCI-E resources on 460EX Ayman El-Khashab
2008-11-03 22:53 ` Felix Radensky
2008-11-04 18:40 ` Henry Bausley
2008-12-01 7:54 ` Benjamin Herrenschmidt
2008-12-01 11:08 ` Felix Radensky
2008-12-01 21:04 ` Benjamin Herrenschmidt
2008-12-02 22:38 ` Felix Radensky
2008-12-04 9:22 ` Felix Radensky
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=490F6882.6050101@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-embedded@ozlabs.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).