From: Marek Olšák marek.ol...@amd.com
---
src/gallium/drivers/radeonsi/si_shader.c | 27
src/gallium/drivers/radeonsi/si_shader.h | 11 +-
src/gallium/drivers/radeonsi/si_state_draw.c | 31 +---
3 files changed, 34 insertions(+),
On Tue, Dec 9, 2014 at 6:39 AM, Marek Olšák mar...@gmail.com wrote:
From: Marek Olšák marek.ol...@amd.com
---
src/gallium/drivers/radeonsi/si_shader.c | 27
src/gallium/drivers/radeonsi/si_shader.h | 11 +-
If clip distances are used, there can be 8 of them. Otherwise, if user
clip planes are used, there can only be 6 of them. If clip vertex is
used, there can still only be 6 clip planes - even though they are
lowered to clip distances.
So first the writemask for clip distances is computed:
On Tue, Dec 9, 2014 at 10:05 AM, Marek Olšák mar...@gmail.com wrote:
If clip distances are used, there can be 8 of them. Otherwise, if user
clip planes are used, there can only be 6 of them. If clip vertex is
used, there can still only be 6 clip planes - even though they are
lowered to clip
It looks like clip planes are deprecated, so you can only use them
with the compatibility profile.
Sure we could support 8 clip planes if ClipVertex is written, but:
- we can only support 6 clip planes if ClipVertex isn't written
- pipe_context::set_clip_state can set only 6 clip planes
Marek
On Tue, Dec 9, 2014 at 10:22 AM, Marek Olšák mar...@gmail.com wrote:
It looks like clip planes are deprecated, so you can only use them
with the compatibility profile.
Right.
Sure we could support 8 clip planes if ClipVertex is written, but:
- we can only support 6 clip planes if ClipVertex
Our hw can only do 6 legacy clip planes without ClipVertex. We would
have to lower them to clip distances to be able to support 8, which is
something I'd rather not do. (there would be more shader work or more
shader variants)
Marek
On Tue, Dec 9, 2014 at 4:29 PM, Ilia Mirkin
