>> Using this means however replacing (in actual use, not in the >> repository, of course) all the GLX/DRI stack with a new Gallium-only >> GLX implementation. > My suggestion for this is still > http://www.mail-archive.com/mesa3d-dev@lists.sourceforge.net/msg10541.html > > I don't think egl_g3d can replace the stock libGL because, at least, it lacks > indirect rendering. Longer term, you might consider revive the Xegl project.
This can be solved by making libGL load a GLX driver. One of them would be egl_g3d, and another the existing code for indirect rendering and legacy DRI. Or possibly some newly written XCB-based indirect rendering GLX driver, if anyone wants to do that. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
