Skip to content

ir3, tu: Use a UBO for VS primitive params on a750+

What does this MR do and why?

ir3, tu: Use a UBO for VS primitive params on a750+

Before we were using direct CP_LOAD_STATE, which is broken with multiple
back-to-back draws. This caused regressions in some DX11 traces when
enabling early preamble. We still need to use indirect CP_LOAD_STATE for
VS params, which are sometimes written by the CP, however for everything
else we should use the new UBO path instead.

Fixes: 76e417ca593 ("turnip,ir3/a750: Implement consts loading via preamble")

Merge request reports