From: "David S. Miller" <davem@redhat.com>
To: Anton Blanchard <anton@samba.org>
Cc: ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: Prefered method to map PCI memory into userspace.
Date: Sat, 27 Sep 2003 16:38:27 -0700 [thread overview]
Message-ID: <20030927163827.241dbb4c.davem@redhat.com> (raw)
In-Reply-To: <20030926135908.GB9381@krispykreme>
On Fri, 26 Sep 2003 23:59:08 +1000
Anton Blanchard <anton@samba.org> wrote:
>
> > Just curious - what does the X server use on these many systems then ?
>
> FYI ppc64 and some ppc32 systems fall into the cant use /dev/mem
> category. The answer is to use pci domains (ie using /proc/bus/pci/...
> to be able to mmap PCI memory and IO regions)
Exactly.
XFREE86-4.3.0 and later has full domain infrastructure, it just isn't
enabled on anything other than ppc and sparc because the other platforms
haven't made their /proc/bus/pci/* mmap() arch support routines fully
functional yet.
next prev parent reply other threads:[~2003-09-27 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Prefered method to map PCI memory into userspace Andi Kleen
2003-09-26 13:59 ` Anton Blanchard
2003-09-27 23:38 ` 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
2003-09-26 20:53 Jim Deas
2003-09-26 21:17 ` Joe Korty
2003-09-27 0:40 ` Benjamin Herrenschmidt
2003-09-27 4:00 ` 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=20030927163827.241dbb4c.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=anton@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.