From: Brian Paul <brianp@vmware.com>
Date: Fri, 7 Jun 2013 16:12:28 +0000 (-0600)
Subject: docs: update some environment variable info
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=90fa71b277e9d4be71a1edf5bc2f2caf7eed0b23;p=mesa.git

docs: update some environment variable info

Drop the GALLIUM_NOSSE/PPC env vars, added ST_DEBUG and some of the
VMware SVGA driver env vars.
---

diff --git a/docs/envvars.html b/docs/envvars.html
index 389da62e6e8..67d8e292bb0 100644
--- a/docs/envvars.html
+++ b/docs/envvars.html
@@ -153,10 +153,6 @@ Mesa EGL supports different sets of environment variables.  See the
     rather than stderr.
 <li>GALLIUM_PRINT_OPTIONS - if non-zero, print all the Gallium environment
     variables which are used, and their current values.
-<li>GALLIUM_NOSSE - if non-zero, do not use SSE runtime code generation for
-    shader execution
-<li>GALLIUM_NOPPC - if non-zero, do not use PPC runtime code generation for
-    shader execution
 <li>GALLIUM_DUMP_CPU - if non-zero, print information about the CPU on start-up
 <li>TGSI_PRINT_SANITY - if set, do extra sanity checking on TGSI shaders and
     print any errors to stderr.
@@ -164,6 +160,9 @@ Mesa EGL supports different sets of environment variables.  See the
 <LI>DRAW_NO_FSE - ???
 <li>DRAW_USE_LLVM - if set to zero, the draw module will not use LLVM to execute
     shaders, vertex fetch, etc.
+<li>ST_DEBUG - controls debug output from the Mesa/Gallium state tracker.
+Setting to "tgsi", for example, will print all the TGSI shaders.
+See src/mesa/state_tracker/st_debug.c for other options.
 </ul>
 
 <h3>Softpipe driver environment variables</h3>
@@ -190,6 +189,16 @@ Mesa EGL supports different sets of environment variables.  See the
     cores present.
 </ul>
 
+<h3>VMware SVGA driver environment variables</h3>
+<ul>
+<li>SVGA_FORCE_SWTNL - force use of software vertex transformation
+<li>SVGA_NO_SWTNL - don't allow software vertex transformation fallbacks
+(will often result in incorrect rendering).
+<li>SVGA_DEBUG - for dumping shaders, constant buffers, etc.  See the code
+for details.
+<li>See the driver code for other, lesser-used variables.
+</ul>
+
 
 <p>
 Other Gallium drivers have their own environment variables.  These may change