Displaying 2 results from an estimated 2 matches for "nvc0_shader_stage".
Did you mean:
nv50_shader_state
2015 May 18
2
[PATCH] nvc0: fix context destruction for partly implemented tesselation
Backtrace:
...
0x00007ffff57fc392 in __assert_fail () from /lib64/libc.so.6
0x00007ffff0cf5bec in nvc0_shader_stage (pipe=<optimized out>) at ./nvc0/nvc0_context.h:204
nvc0_set_constant_buffer (pipe=0x631080, shader=<optimized out>, index=<optimized out>, cb=0x0)
at nvc0/nvc0_state.c:771
0x00007ffff0a2cf63 in st_destroy_context (st=0x68a9f0) at state_tracker/st_context.c:382
...
Signed-off-b...
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