diff options
| author | Samuel Pitoiset <[email protected]> | 2018-12-03 22:45:03 +0100 |
|---|---|---|
| committer | Samuel Pitoiset <[email protected]> | 2018-12-05 09:26:31 +0100 |
| commit | 824cfc1ee5e0aba15b676b9363ff32046d96eb42 (patch) | |
| tree | 70a59a4cf0c3f29a6db55c597aa2d8dc90b135bf /src/util/format_rgb9e5.h | |
| parent | 2669dbf8810c534025ca0dd10942eb416a94fe4d (diff) | |
radv: rework the TC-compat HTILE hardware bug with COND_EXEC
After investigating on this, it appears that COND_WRITE doesn't
work correctly in some situations. I don't know exactly why does
it fail to update DB_Z_INFO.ZRANGE_PRECISION, but as AMDVLK
also uses COND_EXEC I think there is a reason.
Now the driver stores a new metadata value in order to reflect
the last fast depth clear state. If a TC-compat HTILE is fast cleared
with 0.0f, we have to update ZRANGE_PRECISION to 0 in order to
work around that hardware bug.
This fixes rendering issues with The Forest and DXVK and doesn't
seem to introduce any regressions.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108914
Fixes: 68dead112e7 ("radv: update the ZRANGE_PRECISION value for the TC-compat bug")
Signed-off-by: Samuel Pitoiset <[email protected]>
Reviewed-by: Bas Nieuwenhuizen <[email protected]>
Diffstat (limited to 'src/util/format_rgb9e5.h')
0 files changed, 0 insertions, 0 deletions