On Son, 2002-02-10 at 10:31, Gareth Hughes wrote: > These chips can read and write arbitrary locations in system memory. > For all chips that have this feature, the only safe way to program them > is from within a DRM kernel module. Only clients that have been > authenticated via the usual (X auth) means are able to talk to such > modules. There is simply no other way to do it. You can trust the X > server and the kernel module. You CANNOT trust anything else -- a > client-side 3D driver, something masquerading as one, whatever...
I wonder what this means for the current indirect buffer implementation in the r128 driver. It's been pretty much copied and pasted from radeon, I assume these issues have been thought about there? -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
