gallium/docs: fix incorrect/missing references
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Reviewed-by: Brian Paul <brianp@vmware.com>
This commit is contained in:
@@ -31,10 +31,10 @@ CSO objects handled by the context object:
|
|||||||
the CSO module will always replace all samplers at once (no sub-ranges).
|
the CSO module will always replace all samplers at once (no sub-ranges).
|
||||||
This may change in the future.
|
This may change in the future.
|
||||||
* :ref:`Rasterizer`: ``*_rasterizer_state``
|
* :ref:`Rasterizer`: ``*_rasterizer_state``
|
||||||
* :ref:`Depth, Stencil, & Alpha`: ``*_depth_stencil_alpha_state``
|
* :ref:`depth-stencil-alpha`: ``*_depth_stencil_alpha_state``
|
||||||
* :ref:`Shader`: These are create, bind and destroy methods for vertex,
|
* :ref:`Shader`: These are create, bind and destroy methods for vertex,
|
||||||
fragment and geometry shaders.
|
fragment and geometry shaders.
|
||||||
* :ref:`Vertex Elements`: ``*_vertex_elements_state``
|
* :ref:`vertexelements`: ``*_vertex_elements_state``
|
||||||
|
|
||||||
|
|
||||||
Resource Binding State
|
Resource Binding State
|
||||||
@@ -310,7 +310,7 @@ The interface currently includes the following types of queries:
|
|||||||
|
|
||||||
``PIPE_QUERY_OCCLUSION_COUNTER`` counts the number of fragments which
|
``PIPE_QUERY_OCCLUSION_COUNTER`` counts the number of fragments which
|
||||||
are written to the framebuffer without being culled by
|
are written to the framebuffer without being culled by
|
||||||
:ref:`Depth, Stencil, & Alpha` testing or shader KILL instructions.
|
:ref:`depth-stencil-alpha` testing or shader KILL instructions.
|
||||||
The result is an unsigned 64-bit integer.
|
The result is an unsigned 64-bit integer.
|
||||||
This query can be used with ``render_condition``.
|
This query can be used with ``render_condition``.
|
||||||
|
|
||||||
|
@@ -1,4 +1,4 @@
|
|||||||
.. _depth,stencil,&alpha:
|
.. _depth-stencil-alpha:
|
||||||
|
|
||||||
Depth, Stencil, & Alpha
|
Depth, Stencil, & Alpha
|
||||||
=======================
|
=======================
|
||||||
|
@@ -31,7 +31,7 @@ Controls if the :ref:`rbug` should be used.
|
|||||||
|
|
||||||
.. envvar:: GALLIUM_TRACE <string> ("")
|
.. envvar:: GALLIUM_TRACE <string> ("")
|
||||||
|
|
||||||
If set, this variable will cause the :ref:`Trace` output to be written to the
|
If set, this variable will cause the :ref:`trace` output to be written to the
|
||||||
specified file. Paths may be relative or absolute; relative paths are relative
|
specified file. Paths may be relative or absolute; relative paths are relative
|
||||||
to the working directory. For example, setting it to "trace.xml" will cause
|
to the working directory. For example, setting it to "trace.xml" will cause
|
||||||
the trace to be written to a file of the same name in the working directory.
|
the trace to be written to a file of the same name in the working directory.
|
||||||
|
@@ -67,6 +67,8 @@ Softpipe
|
|||||||
|
|
||||||
Reference software rasterizer. Slow but accurate.
|
Reference software rasterizer. Slow but accurate.
|
||||||
|
|
||||||
|
.. _trace:
|
||||||
|
|
||||||
Trace
|
Trace
|
||||||
^^^^^
|
^^^^^
|
||||||
|
|
||||||
|
@@ -1,3 +1,5 @@
|
|||||||
|
.. _resource:
|
||||||
|
|
||||||
Resources and derived objects
|
Resources and derived objects
|
||||||
=============================
|
=============================
|
||||||
|
|
||||||
|
@@ -17,7 +17,7 @@ one.
|
|||||||
|
|
||||||
Some instructions, like :opcode:`I2F`, permit re-interpretation of vector
|
Some instructions, like :opcode:`I2F`, permit re-interpretation of vector
|
||||||
components as integers. Other instructions permit using registers as
|
components as integers. Other instructions permit using registers as
|
||||||
two-component vectors with double precision; see :ref:`Double Opcodes`.
|
two-component vectors with double precision; see :ref:`doubleopcodes`.
|
||||||
|
|
||||||
When an instruction has a scalar result, the result is usually copied into
|
When an instruction has a scalar result, the result is usually copied into
|
||||||
each of the components of *dst*. When this happens, the result is said to be
|
each of the components of *dst*. When this happens, the result is said to be
|
||||||
|
Reference in New Issue
Block a user