Since Keith's tnl_dd_dmatmp.h patches on the 11 Dec last year, the poor i810 has been seriously fubar, I've just gotten time to look at it now (well I've been staring at it on and off for weeks with a blank)
The fix is up at http://freedesktop.org/~airlied/i810_render_fix.diff
I've taken it from the i830 code, and I've modified scale_prim so that the 3rd element is also a fallback case,
This is GL_LINE_LOOP? That makes sense.
Keith can you tell me if my numbers are correct for the i810? or at least where you got the numbers for the i830...
The number is the number of HW vertices emitted per incoming vertex in the fallback path. So for things like
GL_POINTS --> 1 if rendering with a HW point prim
--> 4 if rendering with a HW quad or trifan prim (unlikely)
--> 6 if rendering with 2 triangles GL_LINES --> 1 if rendered with a HW line prim
--> 3 if rendered with 2 tris/line
GL_LINE_LOOP GL_LINE_STRIP --> 2 if rendering with HW line prim 6 if rendered with 2 tris/line
and so on...
if no major objections I'll apply it soon, I'd like to just figure out the values for scale_prim are correct...
fixes, blender and tri sample program among others...
Interesting - this should only be a heuristic to choose the fastest path, not have any correctness value. Correctness should be ensured by i810_validate_render, from t_dd_dmatmp.h. Can you try & find out what's going wrong with that?
Keith
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
