> > 2) xf86dri.h and XF86dri.c that are part of mesa. > > 3) Some of the dri utils from mesa, basically to handle basic drawable > > management and locking. > > > > While doing this I notice that some (3) functions in XF86dri.c are > > depending on Mesa headers and datatypes, and this does not seem to be part > > of the original design, since it makes these files unusable outside Mesa. > > These are > > > > XF86DRICreateDrawable > > XF86DRIDestroyDrawable > > XF86DRICreateContext
I had a few others recently in my getting Radeon vha working, I used a few XF86DRI functions, for now I've just linked libGL but I would like to see them in a low level library.. > > I've been working on factoring out libdrm already, this seems like it would be > an appropriate addition. 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
