tu: Don't actually track seqno's for events
authorConnor Abbott <cwabbott0@gmail.com>
Tue, 9 Jun 2020 13:30:43 +0000 (15:30 +0200)
committerMarge Bot <eric+marge@anholt.net>
Tue, 9 Jun 2020 14:40:52 +0000 (14:40 +0000)
commitf4f6a9be9f639d106055597f21a814b87eb5997b
treee0d52800e9d139b36d1eb39cebadb3c5f0aefed6
parentdfb176a0acf2326d36d4867fc43751e1b7d0d66f
tu: Don't actually track seqno's for events

We just dropped the last user which actually cared about the seqno.
This never worked anyway, since the seqno was never reset between
multiple executions of the same command buffer. Turn the part of the
control buffer which used to track the seqno into a dummy dword, and
figure out automatically whether we need to include it. We will
implement seqnos again eventually, with timline semaphores, but that
will likely be totally different.

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4964>
src/freedreno/vulkan/tu_clear_blit.c
src/freedreno/vulkan/tu_cmd_buffer.c
src/freedreno/vulkan/tu_private.h
src/freedreno/vulkan/tu_query.c