Re: [Mesa-dev] report ARB_cull_distance v3

On 08.05.2016 23:29, Tobias Klausmann wrote: On 08.05.2016 22:50, Ilia Mirkin wrote: What exactly gets fed into the CLIPDIST and CULLDIST semantics? e.g. is CULLDIST[0].x the first cull distance, or is it the first entity in the combined cull/clip distance array? If the former, then this won't

Re: [Mesa-dev] report ARB_cull_distance v3

On 08.05.2016 22:50, Ilia Mirkin wrote: What exactly gets fed into the CLIPDIST and CULLDIST semantics? e.g. is CULLDIST[0].x the first cull distance, or is it the first entity in the combined cull/clip distance array? If the former, then this won't work as implemented on nouveau. If the

Re: [Mesa-dev] report ARB_cull_distance v3

What exactly gets fed into the CLIPDIST and CULLDIST semantics? e.g. is CULLDIST[0].x the first cull distance, or is it the first entity in the combined cull/clip distance array? If the former, then this won't work as implemented on nouveau. If the latter, then why bother with the separate

[Mesa-dev] report ARB_cull_distance v3

After the cleanup of my patches in v2, this is another take on finishing this extension. v2: cleanup, reordering of patches, split lowering pass adapation (Dave Airlie) v3: - drop wrong codesection for array size check (suggested by Timothy Arceri) and with it the now useless helper to see

Re: [Mesa-dev] report ARB_cull_distance

Patches 1-5, 8 & 10 are, Reviewed-by: Edward O'Callaghan On 2016-04-04 12:15, Dave Airlie wrote: Okay I've taken Tobias' last work in progress, cleaned it up a bit, move the rename out into a separate patch, reordered things slightly. I've dropped the separate

[Mesa-dev] report ARB_cull_distance

Okay I've taken Tobias' last work in progress, cleaned it up a bit, move the rename out into a separate patch, reordered things slightly. I've dropped the separate passes, I think nearly all hw operates the same, I do wonder why we even have this as an option, since at least 965/gallium always