Displaying 3 results from an estimated 3 matches for "nvc0_gmtyprog_validate".
Did you mean:
nv50_gmtyprog_validate
2015 Jul 11
2
[PATCH] nvc0: fix geometry program revalidation of clipping params
...s/nouveau/nvc0/nvc0_state_validate.c
+++ b/src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c
@@ -339,7 +339,7 @@ nvc0_check_program_ucps(struct nvc0_context *nvc0,
nvc0_vertprog_validate(nvc0);
else
if (likely(vp == nvc0->gmtyprog))
- nvc0_vertprog_validate(nvc0);
+ nvc0_gmtyprog_validate(nvc0);
else
nvc0_tevlprog_validate(nvc0);
}
--
2.3.6
2015 Jul 13
2
[Mesa-dev] [PATCH] nvc0: fix geometry program revalidation of clipping params
.../drivers/nouveau/nvc0/nvc0_state_validate.c
>> @@ -339,7 +339,7 @@ nvc0_check_program_ucps(struct nvc0_context *nvc0,
>> nvc0_vertprog_validate(nvc0);
>> else
>> if (likely(vp == nvc0->gmtyprog))
>> - nvc0_vertprog_validate(nvc0);
>> + nvc0_gmtyprog_validate(nvc0);
>> else
>> nvc0_tevlprog_validate(nvc0);
>> }
>> --
>> 2.3.6
>>
>> _______________________________________________
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/lis...
2015 May 17
14
[PATCH 00/12] Tessellation support for nvc0
This is enough to enable tessellation support on nvc0. It seems to
work a lot better on my GF108 than GK208. I suspect that there's some
sort of scheduling shenanigans that need to be adjusted for
kepler+. Or perhaps some shader header things.
Even with the GF108, I still get occasional blue triangles in Heaven,
but I get a *ton* of them on the GK208 -- seemingly the same issue,
but it's