linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: joe.korty@ccur.com
Cc: Jim Deas <jdeas@jadsystems.com>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Prefered method to map PCI memory into userspace.
Date: Sat, 27 Sep 2003 02:40:10 +0200	[thread overview]
Message-ID: <1064623209.631.26.camel@gaston> (raw)
In-Reply-To: <20030926211740.GA27352@tsunami.ccur.com>


> 
> Albert Cahalan wrote a patch, for 2.6, that makes mmappable all PCI device
> memory regions.  They show up as files in the appropriate subdirectories
> under /proc/bus/pci.  See http://lkml.org/lkml/2003/7/13/258 for the
> patch and details.

mmap of /proc/bus/pci is a standard thing in 2.4 already and so in 2.6
as well, though not all archs may implement it..

Regarding bus mastering, there's no way to do that without a kernel
driver.

Ben.



  reply	other threads:[~2003-09-27  0:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 20:53 Prefered method to map PCI memory into userspace Jim Deas
2003-09-26 21:17 ` Joe Korty
2003-09-27  0:40   ` Benjamin Herrenschmidt [this message]
2003-09-27  4:00     ` David S. Miller
     [not found] <1064609623.16160.11.camel@ArchiveLinux.suse.lists.linux.kernel>
2003-09-26 22:03 ` Andi Kleen
2003-09-27  4:01   ` David S. Miller
     [not found] ` <20030926211740.GA27352@tsunami.ccur.com.suse.lists.linux.kernel>
     [not found]   ` <1064623209.631.26.camel@gaston.suse.lists.linux.kernel>
     [not found]     ` <20030926210034.3a1b4de7.davem@redhat.com.suse.lists.linux.kernel>
2003-09-27  5:09       ` Andi Kleen
2003-09-27 23:39         ` David S. Miller
     [not found] <A8WS.6Uf.9@gated-at.bofh.it>
     [not found] ` <A8WR.6Uf.7@gated-at.bofh.it>
     [not found]   ` <Aezg.6hA.9@gated-at.bofh.it>
2003-09-27  4:42     ` Andi Kleen
2003-09-26 13:59       ` Anton Blanchard
2003-09-27 23:38         ` David S. Miller

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=1064623209.631.26.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jdeas@jadsystems.com \
    --cc=joe.korty@ccur.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;
as well as URLs for NNTP newsgroup(s).