diff options
| author | Roland Scheidegger <sroland@vmware.com> | 2010-02-03 18:27:32 +0100 |
|---|---|---|
| committer | Roland Scheidegger <sroland@vmware.com> | 2010-02-03 18:27:32 +0100 |
| commit | 8091e73cc2142945c297191a9b746be71360ef26 (patch) | |
| tree | 8084682a95bb101b5d315e94a25cadf1db3338a2 | |
| parent | c2b85e335dd798facb8ec43a4bb00fe0e05cf863 (diff) | |
docs: clean up TGSI_SEMANTIC_PSIZE description
there was some confusion between point size state and point size output.
| -rw-r--r-- | src/gallium/docs/source/tgsi.rst | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/src/gallium/docs/source/tgsi.rst b/src/gallium/docs/source/tgsi.rst index ebee4902b0..ef068448e8 100644 --- a/src/gallium/docs/source/tgsi.rst +++ b/src/gallium/docs/source/tgsi.rst @@ -1231,10 +1231,8 @@ TGSI_SEMANTIC_PSIZE """"""""""""""""""" PSIZE, or point size, is used to specify point sizes per-vertex. It should -be in ``(p, n, x, f)`` format, where ``p`` is the point size, ``n`` is the minimum -size, ``x`` is the maximum size, and ``f`` is the fade threshold. - -XXX this is arb_vp. is this what we actually do? should double-check... +be in ``(s, 0, 0, 1)`` format, where ``s`` is the (possibly clamped) point size. +Only the first component matters when writing from the vertex shader. When using this semantic, be sure to set the appropriate state in the :ref:`rasterizer` first. |