> > My issue with exposing XF86DRI* as they are now is that they're direct > bindings to the XFree86-DRI protocol, which I don't think should be > app-visible at all. Consider the possibility of someone wanting to write a > DRI server that was not an X server. We should be enabling our competition.
If your app is DRI aware but not OpenGL i.e. XvMC then it is nice to have these... ATI's dodgy VHA uses them as well.. at the moment I'm not even close to starting on the XvMC implementation,, just decrypting the assembler is taking most of my time.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
