Prefered method to map PCI memory into userspace.
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]
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/memPIO cannot be done on memory, for that you have to use
iopl()orioperm()to get access to the port and then issue the PIO instructions yourselfPlatform dependant, mmap on
/dev/memdoesn't work on many systems.
Just curious - what does the X server use on these many systems then ?
-Andi
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
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/memcategory. 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.