> 4. svgalib allocates a virtual frame buffer (at VBF), and copies the
> physical one to it.
>
> 5. svgalib calls mmap(GM,0x10000,,,proc_self_mem_fd,VBF), so that
> writes at 0x4321xxxx go to the virtual frame buffer, and not to the
> physical one.
>
> Now, step 5 is broken. Is the same result (that of the mmap in
> step 5) achievable by other means?
Yes. Use anonymous mmap on the step 4 and mremap on step 5.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/