summaryrefslogtreecommitdiffstats
path: root/docs/features.txt
diff options
context:
space:
mode:
authorJuan A. Suarez Romero <[email protected]>2019-02-22 16:47:53 +0100
committerJuan A. Suarez Romero <[email protected]>2019-02-22 17:53:55 +0100
commit4f917e6a61860b58a05d40584f7aa3d5e4e32b75 (patch)
tree244a81d2b95e634004dc8962e6487fbe8812eda9 /docs/features.txt
parent3b423eeb2d326418147fdfbdc89a415e44a557d3 (diff)
anv: advertise 8 subpixel precision bits
On one side, when emitting 3DSTATE_SF, VertexSubPixelPrecisionSelect is used to select between 8 bit subpixel precision (value 0) or 4 bit subpixel precision (value 1). As this value is not set, means it is taking the value 0, so 8 bit are used. On the other side, in the Vulkan CTS tests, if the reference rasterizer, which uses 8 bit precision, as it is used to check what should be the expected value for the tests, is changed to use 4 bit as ANV was advertising so far, some of the tests will fail. So it seems ANV is actually using 8 bits. v2: explicitly set 3DSTATE_SF::VertexSubPixelPrecisionSelect (Jason) v3: use _8Bit definition as value (Jason) v4: (by Jason) anv: Explicitly set 3DSTATE_CLIP::VertexSubPixelPrecisionSelect This field was added on gen8 even though there's an identically defined one in 3DSTATE_SF. CC: Jason Ekstrand <[email protected]> CC: Kenneth Graunke <[email protected]> CC: 18.3 19.0 <[email protected]> Signed-off-by: Juan A. Suarez Romero <[email protected]> Reviewed-by: Lionel Landwerlin <[email protected]> Reviewed-by: Jason Ekstrand <[email protected]>
Diffstat (limited to 'docs/features.txt')
0 files changed, 0 insertions, 0 deletions