braodcom/vc5: Rely on OVRTMUOUT always being set.
authorEric Anholt <eric@anholt.net>
Fri, 29 Dec 2017 19:48:41 +0000 (11:48 -0800)
committerEric Anholt <eric@anholt.net>
Wed, 3 Jan 2018 22:25:23 +0000 (14:25 -0800)
commit476469955225e15f454e01dc80047dd5fa5c9f97
tree57ea220e209807c33f0eed0c70c0a57863beeecb
parentba965084b60e702b41beaea75237bfa39335b6cb
braodcom/vc5: Rely on OVRTMUOUT always being set.

It seems that the HW team has decided that it's the only supported mode,
and it's the mode I actually meant to be using but forgot.  Our table of
return_32_bit should have matched the default non-OVRTMUOUT behavior, so
this change should be invisible.

However, the change revealed that some my return_size checks for swizzling
were a bit confused in the shadow case, so I had to move them to draw time
once we have both the sampler and the view together.

Fixes assertion failures in the updated simulator, where the non-OVRTMUOUT
support has been removed.
src/broadcom/cle/v3d_packet_v33.xml
src/gallium/drivers/vc5/vc5_context.h
src/gallium/drivers/vc5/vc5_emit.c
src/gallium/drivers/vc5/vc5_formats.c
src/gallium/drivers/vc5/vc5_program.c
src/gallium/drivers/vc5/vc5_simulator.c
src/gallium/drivers/vc5/vc5_state.c