Hello, I plan to merge gallium-edgeflags branch soon. I should have fixed up drivers syntactically, but note some will break if applications use edgeflags. In particular the drivers which so far have chosen to ignore edgeflags completely and don't have implemented a fall back to use the draw module might break (I'm looking at you, r300 and nv30!...). If those drivers want to continue to just have broken edgeflags support but you just don't want them to crash, you'll need to fix them up so they map the edgeflag output of the vertex shader to something halfway meaningful for the hw, like a unneeded temp or so. But really the right solution is to fix them so they use the draw module for things they can't handle, like svga and nv40 do (or, of course, make them handle edgeflags properly in hardware, but that might be dx10-class hardware only which truly can do it). Drivers for hardware without a hw vertex unit shouldn't have any problem, since draw will handle everything for them. You can use progs/trivial/tri-edgeflag for instance to see what happens.
Roland ------------------------------------------------------------------------------ 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
