search for: cliporculldist

Displaying 5 results from an estimated 5 matches for "cliporculldist".

2015 May 25
2
[RFC PATCH 00/11] Implement ARB_cull_distance
On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: > It's the same on Radeon. There are 2x ClipOrCullDistance output > vectors and a mask saying it should clip or cull or do nothing. > > Marek > My thinking was gallium should have a single semantic and a mask in the shader definition maybe. though it doesn't solve the does nvidia do the right thing with cull[0] and clip[0], and what is...
2015 May 25
4
[RFC PATCH 00/11] Implement ARB_cull_distance
...5, 2015 at 9:40 AM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > > On 25.05.2015 07:17, Dave Airlie wrote: >> >> On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: >>> >>> It's the same on Radeon. There are 2x ClipOrCullDistance output >>> vectors and a mask saying it should clip or cull or do nothing. >>> >>> Marek >>> >> My thinking was gallium should have a single semantic and a mask in >> the shader definition maybe. >> >> though it doesn't solve the d...
2015 May 24
2
[RFC PATCH 00/11] Implement ARB_cull_distance
...gt; look like? I'm not even sure. > > Do you want to have a separate 2x CLIPDIST and 2x CULLDIST and let the > driver worry about figuring out the max clip dist used and sticking > the cull dists above it? Or do you want to work it out at a lower > level where they share a single CLIPORCULLDIST semantic and get a > separate e.g. shader property that gives them the mask? > > I don't know how other hardware works, but nv50/nvc0 hw has 8 > clip_or_cull distances, and a mask that selects whether each is a clip > or a cull distance. But perhaps other hw has them totally sepa...
2015 May 24
2
[RFC PATCH 00/11] Implement ARB_cull_distance
On 24.05.2015 20:25, Ilia Mirkin wrote: > I'm having a bit of trouble tracing through this. What happens if I > have a shader that just does: > > gl_ClipDistance[0] = 1; > gl_CullDistance[0] = 1; > > what does the resulting TGSI look like? (Assuming that clip plane 0 is > enabled.) What about the generated nvc0 code (for the vertex shader)? (hack up a patch for this,
2015 May 27
2
[RFC PATCH 00/11] Implement ARB_cull_distance
...5 at 9:40 AM, Tobias Klausmann >> <tobias.johannes.klausmann at mni.thm.de> wrote: >>> On 25.05.2015 07:17, Dave Airlie wrote: >>>> On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: >>>>> It's the same on Radeon. There are 2x ClipOrCullDistance output >>>>> vectors and a mask saying it should clip or cull or do nothing. >>>>> >>>>> Marek >>>>> >>>> My thinking was gallium should have a single semantic and a mask in >>>> the shader definition maybe. &gt...