diff options
author | Ilia Mirkin <[email protected]> | 2015-04-07 11:43:52 -0400 |
---|---|---|
committer | Ilia Mirkin <[email protected]> | 2015-04-18 18:27:09 -0400 |
commit | 1cdb01d716cb8112c67f8538f7d71d0765153eb2 (patch) | |
tree | 4f88f33064bf1c3570f93fbd38458cae04e2f9e3 /src | |
parent | 0904774af1ff9202863e7c935ff9bc076d533fb3 (diff) |
primconvert: select pv convention only from flatshade_first
This should match to how drivers program hardware. flatshade relates to
whether color inputs are interpolated, not the provoking vertex
convention.
Signed-off-by: Ilia Mirkin <[email protected]>
Reviewed-by: Rob Clark <[email protected]>
Diffstat (limited to 'src')
-rw-r--r-- | src/gallium/auxiliary/indices/u_primconvert.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/gallium/auxiliary/indices/u_primconvert.c b/src/gallium/auxiliary/indices/u_primconvert.c index 00e65aaea31..70d3e8530b8 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 |