gallium/hud: do not specify potentially invalid depth-range
authorErik Faye-Lund <erik.faye-lund@collabora.com>
Tue, 9 Jun 2020 19:25:26 +0000 (21:25 +0200)
committerMarge Bot <eric+marge@anholt.net>
Wed, 10 Jun 2020 22:27:08 +0000 (22:27 +0000)
commit67ad75a282d11f4c284e30ddc8848550f02a6948
tree6f2c9efac8de8e17c9aff2a890fd1d43e318b665
parent978285f69a4ac9a17afbcdac5f36eebab4f14269
gallium/hud: do not specify potentially invalid depth-range

Setting the depth-scale to 1 while leaving the depth-translation at 0
means our near-plane is at -1 in OpenGL semantics, which is
out-of-range on some drivers. In particular, Zink has this limitation.

But since we'll only pass a zero z in here anyway, we might as well
multiply it by zero, and get the same result. This avoids the problem.

Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5408>
src/gallium/auxiliary/hud/hud_context.c