Thread (12 messages) 12 messages, 6 authors, 1999-12-01

Re: Frame buffer / mmap() weirdness

From: Michael Schmitz <hidden>
Date: 1999-12-01 11:12:09

quoted
quoted
I think it will make munmap() more difficult to implement. Furthermore I see no
provisions for this in the current mmap() code. And it will break backwards
compatibility.
Don't know for mmap(), but it seems the only change to munmap() is
to clear the appropriate number of low-order bits in its first argument
( addr & 0xfffff000 for 32-bit machines with 4k page size).
You are right. Since I guess the other mmap()s in the kernel are POSIX
compliant, I feel silly now.
It will still break backwards compatibility (i.e. old X servers). We can
catch the case of old kernels used with new X servers but not the other
way. 

Either way - I recall getting errors from the generic mmap code when
passing not page aligned addresses back from fb_mmap. Has something
changed in the mmap code to remove this restriction? 

	Michael

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help