From f3b37e321fe5ea8a8c0ff026636d69ce90437a6f Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Sun, 27 Sep 2015 19:32:07 +0200 Subject: gallium: add per-sample interpolation control into rasterizer statOAe Required by ARB_sample_shading for drivers that don't want a shader variant in st/mesa. Reviewed-by: Ilia Mirkin Acked-by: Roland Scheidegger --- src/gallium/docs/source/screen.rst | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'src/gallium/docs/source/screen.rst') diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index e7800472f44..e08844b2f0b 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -268,6 +268,15 @@ The integer capabilities: bounds_max states of pipe_depth_stencil_alpha_state behave according to the GL_EXT_depth_bounds_test specification. * ``PIPE_CAP_TGSI_TXQS``: Whether the `TXQS` opcode is supported +* ``PIPE_CAP_FORCE_PERSAMPLE_INTERP``: If the driver can force per-sample + interpolation for all fragment shader inputs if + pipe_rasterizer_state::force_persample_interp is set. This is only used + by GL3-level sample shading (ARB_sample_shading). GL4-level sample shading + (ARB_gpu_shader5) doesn't use this. While GL3 hardware has a state for it, + GL4 hardware will likely need to emulate it with a shader variant, or by + selecting the interpolation weights with a conditional assignment + in the shader. + .. _pipe_capf: -- cgit v1.2.3