On Sun, 2004-03-14 at 07:14, Jon Smirl wrote: > This is a first pass at the three new IOCTL patch. > > It is against the DRM copy in the Mesa tree.
And exactly why does that still exist? I know you don't listen to me, but I don't think you can ignore Keith. > 2) It uses the kernel to bind the DRM driver to the video device. This will make > it conflict with framebuffer. You will have to uninstall framebuffer before it > can be loaded. The kernel does not allow two device drivers to bind to the same > device. (DRM currently functions by accessing the device without telling the > kernel it is going to do so). > > Next pass I will add ifdef's on the kernel device binding. If you turn off > kernel device binding you will also lose sysfs support and hotplug reset > support. I hope you manage to keep working setups working this time... > Since there is no sysfs support you won't get EDID in sysfs and mode > setting won't work. Speaking of mode setting: AFAICT the user supplied register values aren't checked at all, yet the ioctl isn't restricted to root. One or the other will have to be done. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
