Module: Mesa Branch: gallium-clip-state Commit: cfec82bca3fefcdefafca3f4555285ec1d1ae421 URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=cfec82bca3fefcdefafca3f4555285ec1d1ae421
Author: Christoph Bumiller <[email protected]> Date: Fri Jan 6 14:16:51 2012 +0100 gallium/docs: update for clip state changes --- src/gallium/docs/source/cso/rasterizer.rst | 14 ++++++++++++++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/src/gallium/docs/source/cso/rasterizer.rst b/src/gallium/docs/source/cso/rasterizer.rst index a3836d9..482b1ea 100644 --- a/src/gallium/docs/source/cso/rasterizer.rst +++ b/src/gallium/docs/source/cso/rasterizer.rst @@ -227,3 +227,17 @@ gl_rasterization_rules Whether the rasterizer should use (0.5, 0.5) pixel centers. When not set, the rasterizer will use (0, 0) for pixel centers. +depth_clip + When false, the near and far depth clipping planes of the view volume are + disabled and the depth value will be clamped at the per-pixel level, after + polygon offset has been applied and before depth testing. + +clip_plane_enable + For each k in [0, PIPE_MAX_CLIP_PLANES), if bit k of this field is set, + clipping half-space k is enabled, if it is clear, it is disabled. + The clipping half-spaces are defined either by the user clip planes in + ``pipe_clip_state``, or by the clip distance outputs of the shader stage + preceding the fragment shader. + If any clip distance output is written, those half-spaces for which no + clip distance is written count as disabled; i.e. user clip planes and + shader clip distances cannot be mixed, and clip distances take precedence. _______________________________________________ mesa-commit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-commit
