From: "David S. Miller" <davem@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: joe.korty@ccur.com, jdeas@jadsystems.com, linux-kernel@vger.kernel.org
Subject: Re: Prefered method to map PCI memory into userspace.
Date: Fri, 26 Sep 2003 21:00:34 -0700 [thread overview]
Message-ID: <20030926210034.3a1b4de7.davem@redhat.com> (raw)
In-Reply-To: <1064623209.631.26.camel@gaston>
On Sat, 27 Sep 2003 02:40:10 +0200
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 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..
If someone is looking for something to do, it would be incredibly
value to make it so that all arches support this, and in particular
get right the case of mmap()'ing the PCI host bridge.
If this were done, the PCI domain code in xfree86 could be enabled
for all Linux platforms, not just the ones that have this implemented
properly.
next prev parent reply other threads:[~2003-09-27 4:01 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
2003-09-27 4:00 ` David S. Miller [this message]
[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=20030926210034.3a1b4de7.davem@redhat.com \
--to=davem@redhat.com \
--cc=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).