From 8acaf862dfeac62550514b0e46f5aa6212b08992 Mon Sep 17 00:00:00 2001 From: Christoph Bumiller Date: Fri, 15 Mar 2013 22:11:31 +0100 Subject: gallium: add TGSI_SEMANTIC_TEXCOORD,PCOORD v3 This makes it possible to identify gl_TexCoord and gl_PointCoord for drivers where sprite coordinate replacement is restricted. The new PIPE_CAP_TGSI_TEXCOORD decides whether these varyings should be hidden behind the GENERIC semantic or not. With this patch only nvc0 and nv30 will request that they be used. v2: introduce a CAP so other drivers don't have to bother with the new semantic v3: adapt to introduction gl_varying_slot enum --- src/gallium/docs/source/cso/rasterizer.rst | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/gallium/docs/source/cso/rasterizer.rst') diff --git a/src/gallium/docs/source/cso/rasterizer.rst b/src/gallium/docs/source/cso/rasterizer.rst index f4e24f0b438..8338243be9f 100644 --- a/src/gallium/docs/source/cso/rasterizer.rst +++ b/src/gallium/docs/source/cso/rasterizer.rst @@ -159,13 +159,18 @@ Points sprite_coord_enable ^^^^^^^^^^^^^^^^^^^ +The effect of this state depends on PIPE_CAP_TGSI_TEXCOORD ! Controls automatic texture coordinate generation for rendering sprite points. +If PIPE_CAP_TGSI_TEXCOORD is false: When bit k in the sprite_coord_enable bitfield is set, then generic input k to the fragment shader will get an automatically computed texture coordinate. +If PIPE_CAP_TGSI_TEXCOORD is true: +The bitfield refers to inputs with TEXCOORD semantic instead of generic inputs. + The texture coordinate will be of the form (s, t, 0, 1) where s varies from 0 to 1 from left to right while t varies from 0 to 1 according to the state of 'sprite_coord_mode' (see below). -- cgit v1.2.3