On Thu, Jul 16, 2015 at 8:05 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> There is no need for this.
>
> v2: handle redundant clip state changes in st/mesa
> ---
> src/gallium/auxiliary/cso_cache/cso_context.c | 44
> ---
> src/gallium/auxiliary/cso_cache/cso_context.h
From: Marek Olšák
There is no need for this.
v2: handle redundant clip state changes in st/mesa
---
src/gallium/auxiliary/cso_cache/cso_context.c | 44 ---
src/gallium/auxiliary/cso_cache/cso_context.h | 13
src/mesa/state_tracker/st_atom_clip.c | 7 +++
Sssort of. But drivers that were expecting this to happen will now
need to do the compare themselves. For example nv50 (and I assume
nvc0) just always copy the new values in and set the dirty flag.
Really you're just pushing this down into the driver, which is
reasonable, but in the process you're
From: Marek Olšák
There is no need for this.
---
src/gallium/auxiliary/cso_cache/cso_context.c | 44 ---
src/gallium/auxiliary/cso_cache/cso_context.h | 13
src/mesa/state_tracker/st_atom_clip.c | 2 +-
3 files changed, 1 insertion(+), 58 deletions(-)
d
