mmap(), Solaris 2.1 x86, and > real memory.

mmap(), Solaris 2.1 x86, and > real memory.

Post by David Holla » Sat, 22 Jan 1994 03:13:48


Hopefully someone can answer this for me.

Is it possible to mmap() addresses that are greater than real memory?

I'm trying to mmap the 4MB linear appature on a Mach32 VLB board back
into user address space.  The usual location the Mach32 board decodes
its appature is at 124Mb, obviously there's not that much memory in the
machine.  So is there a way to mmap() from 124Mb to 128Mb back into
user space?

a basic open()/mmap() of /dev/mem doesn't allow it. It returns
the expect error (Invalid address or something like that).
The /dev/vtXX devices only seem to allow access from 0xA0000, to 0xFFFFF.

Perhaps there's a ioctl() someplace that I'm missing that tells
the memory device driver to turn off its range checking?

Many thanks!

David Holland
David Holland

Dream another dream, this dream is over. (Van Halen)


1. Memory mapping SVGA video memory on Solaris 2.1 x86??

Does anyone out there know of any problems/pitfalls when trying to memory map /dev/vt01?
I have an application that does this and the mmap() is failing with a "no such device.." error.
I'm trying to memory map my SVGA video memory.

Any help/pointers would be greatly appreciated!

Thanks in advance,


Doug Anson                                      

Phone:    713.560.1274
FAX:      713.560.1277
SNAIL:    Landmark Graphics Corporation LGC    
          15150 Memorial Drive
          Houston, TX 77079                    


3. Solaris 2.1 X86 mmap driver problem

4. Priority Mechanism in Linux

5. Shared memory, Semaphores, and Solaris 2.1 for x86

6. soundblaster 32 AWE

7. XFree86 2.1 for solaris x86 2.1

8. tracking anonymous ftp service

9. Solaris 2.1 x86 OEM:Standalone -> network ?

10. < FAS/SAS for Solaris 2.1 x86 ? >

11. Solaris X86 + >2.1 Gb IDE Disk?

12. mmap'ed access to VMEmem space under Solaris 2.1

13. Solaris 2.1 printing sucks (was Re: problem with lpstat with Solaris 2.1)