mesa,gallium: Revert "Make point coord origin a CAP"
This reverts commite749f67f89
, which added a CAP to support drivers that can only do upside-down point coordinates. That was added specifically for Asahi, since Metal's point coordinate convention is opposite Mesa's. Since then, additional reverse-engineering aided by the PowerVR headers led me to the bit doing the flip in hardware, so Asahi does not use the CAP sincebaadc1ec13
("asahi: Don't use lower_wpos_pntc"). Garbage collect it. [If it's needed for future hardware, we can revive it. But the plan is Vulkan anyway.] Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Suggested-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19078>
This commit is contained in:

committed by
Marge Bot

parent
86c9aa6bfe
commit
4c7a44413a
@@ -71,8 +71,6 @@ The integer capabilities:
|
||||
pixel-center fragment convention is supported.
|
||||
* ``PIPE_CAP_FS_COORD_PIXEL_CENTER_INTEGER``: Whether the integer
|
||||
pixel-center fragment convention is supported.
|
||||
* ``PIPE_CAP_POINT_COORD_ORIGIN_UPPER_LEFT``: Whether point coordinates use the
|
||||
upper-left origin convention. Otherwise the lower-left convention is used.
|
||||
* ``PIPE_CAP_DEPTH_CLIP_DISABLE``: Whether the driver is capable of disabling
|
||||
depth clipping (through pipe_rasterizer_state).
|
||||
* ``PIPE_CAP_DEPTH_CLIP_DISABLE_SEPARATE``: Whether the driver is capable of
|
||||
|
Reference in New Issue
Block a user