Hi !
> > hardware auxiliary buffer, you will either need to have a kernel driver
> > which can let userspace mmap() the physical aperture, or do some suid-root
> Neither. The SGI approach of not mmaping these buffers.
This only works for the nice SGI hardware. I perfectly agree, that it has
huge benefits to not allow framebuffer or other auxiliary buffer access.
And it is the right thing to do, if the hardware is nicely built and can do
most stuff by itself and accelerated.
However for most PC hardware, forget about it. We have to use a kerneldriver
to protect that buggy pieces of HW from crashing by malicious or careless
user programs, and jumping to Kernel for each putpixel isn't an option
performance-wise.
You need to be able to do a bunch of overlaying putpixels or similar by mmap
acccess, if you don't want to crawl.
> I rather set a flag to tell the system to use a particular buffer.
That implies that the system is capable of doing _all_ drawing operations
itself and can do so _quickly_.
CU, ANdy
--
Andreas Beck | Email : <[EMAIL PROTECTED]>
