This should match to how drivers program hardware. It shouldn't matter
when flatshading isn't in effect, but somehow it seems to.
Signed-off-by: Ilia Mirkin <imir...@alum.mit.edu>
---
src/gallium/auxiliary/indices/u_primconvert.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/gallium/auxiliary/indices/u_primconvert.c
b/src/gallium/auxiliary/indices/u_primconvert.c
index 00e65aa..70d3e85 100644
--- a/src/gallium/auxiliary/indices/u_primconvert.c
+++ b/src/gallium/auxiliary/indices/u_primconvert.c
@@ -104,8 +104,7 @@ util_primconvert_save_rasterizer_state(struct
primconvert_context *pc,
* we would actually need to save/restore rasterizer state. As
* it is, we just need to make note of the pv.
*/
- pc->api_pv = (rast->flatshade
- && !rast->flatshade_first) ? PV_LAST : PV_FIRST;
+ pc->api_pv = rast->flatshade_first ? PV_FIRST : PV_LAST;
}
void
--
2.0.5
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
