From: Jiri Slaby <jirislaby@gmail.com>
To: joncglenn <joncglenn@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mapping PCI memory to user-space
Date: Wed, 24 Oct 2007 09:52:45 +0200 [thread overview]
Message-ID: <471EF9CD.6070400@gmail.com> (raw)
In-Reply-To: <13380086.post@talk.nabble.com>
On 10/24/2007 08:59 AM, joncglenn wrote:
> I am writing a driver to map a PCI board memory space (pcibar2) into a
> user-space vma via 'mmap'. What is the relationship between the address
> returned from ioremap and the type of address needed in the
> 'io_remap_page_range' or 'remap_pfn_range' functions? How about the
> following? (I am developing under RHEL4 and a 2.6.9 kernel)
I think you can use the method used for exporting pci resources in /sys. See
pci_mmap_resource. Don't know if this was yet in 2.6.9...
regards,
--
Jiri Slaby (jirislaby@gmail.com)
Faculty of Informatics, Masaryk University
next prev parent reply other threads:[~2007-10-24 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 6:59 Mapping PCI memory to user-space joncglenn
2007-10-24 7:52 ` Jiri Slaby [this message]
2007-10-28 3:06 ` Roland Dreier
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=471EF9CD.6070400@gmail.com \
--to=jirislaby@gmail.com \
--cc=joncglenn@hotmail.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