Skip to contentSkip to conversation

Prefered method to map PCI memory into userspace.

DISCUSSION Andi Kleen 3 participants 3 messages Sep 27, 2003 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#3 lore raw
Quoted 10 lines · David S. Miller
Quoted 5 lines · On 27 Sep 2003 00:03:42 +0200 Andi Kleen <[email protected]> wrote:

mmap on /dev/mem

PIO cannot be done on memory, for that you have to use iopl() or ioperm() to get access to the port and then issue the PIO instructions yourself

Platform dependant, mmap on /dev/mem doesn't work on many systems.

Just curious - what does the X server use on these many systems then ?

-Andi

#4 lore raw
Quoted 2 lines

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)

Anton

#5 lore raw
Quoted 6 lines · On Fri, 26 Sep 2003 23:59:08 +1000 Anton Blanchard <[email protected]> wrote:
Quoted 2 lines

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.