I've committed a new driver to src/mesa/drivers/dri/x11. It's basically a pure-fallback driver like drivers/dri/fb, only it uses X's GLX instead of miniglx. It's not done yet but it's good enough to get direct rendering: Yes and run GL programs (they won't draw anything though).
What's the point of this? First, it can be used as a skeleton driver for people adding new hardware support. Second, if the X server can be taught to load this sort of driver instead of the libGLcore sort, then we can get accelerated indirect rendering for free. Current thinking is that this method is easier than fixing up libGLcore/libglx to match libGL.so/foo_dri.so. The core doesn't know about this driver yet, so if you want to test it out, point LIBGL_DRIVERS_PATH at the containing directory, and make a symlink from r200_dri.so (or whatever) pointing to x11_dri.so. Be sure to add x11 to DRI_DIRS (if building from Mesa) or DriDrivers (if building from xc). The problem with just kicking all the rendering down the drivers/x11 code is that drivers/x11 has a slightly different set of structs than what the DRI expects. One could probably encapsulate XMesaContexts inside the private fields, but that's kinda ugly. Testing and further hacking is encouraged. - ajax ------------------------------------------------------- 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
