Quoting Keith Whitwell ([EMAIL PROTECTED]): > Brian Paul wrote: > >> > >> dri/ - dri driver interface > >> api/ - public api > >> common/ - reusable driver code > >> radeon/ - DRI driver > >> r200/ - DRI driver > >> mga/ - DRI driver > > > > > >What's the "public api"? > > Hmm, maybe the libGL code?
That's the public API of DRI Mesa. It's where DRIMesaCreateContext and DRIMesaCreateDrawable etc. reside, like fxMesaCreateContext in drivers/glide/ or OSMesaCreateContext in drivers/osmesa/. MiniGLX, XF86 GLX and DirectFBGL will use this API. Even plain framebuffer device based applications could use DRI, too, e.g. SDL on the framebuffer device wouldn't need that much code to add hardware accelerated OpenGL support. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
