> > The idea is to reduce the kernel mod to nothing more then device > > enumeration and detection. > > However you solve it.. I don't care about how the kernel driver <--> > userspace driver interface is defined or implemented. I just don't think > there should be one interface for all devices, as it is now with DRM. > The userspace dri driver is the only user of these kernel drivers. > As each device works differently, why don't adapt this interface to each > device. > With the current design, there are three interfaces: dri (in userspace), > drm (between kernel and userspace) and Mesa (opengl). Why don't define > only on interface (opengl) so each driver can be optimized as much as > possible. Then make packages with kernel driver/userspace driver pairs > for each card that can be compiled separately (without any other > prerequisites).
you really should read up on the overall DRI/DRM, the interface isn't one fits all, theree is a common part which an author can use if they want and there is a card specific part, reading http://dri.sourceforge.net/doc/drm_low_level.html perhaps might help although it is a bit out of date... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
