docs: softpipe -> Softpipe

Reviewed-by: Yonggang Luo <luoyonggang@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19297>

docs/ci/index.rst

@@ -15,7 +15,7 @@ The CI runs a number of tests, from trivial build-testing to complex GPU renderi
 
 - Build testing for a number of build systems, configurations and platforms
 - Sanity checks (``meson test``)
-- Some drivers (softpipe, LLVMpipe, Freedreno and panfrost) are also tested
+- Some drivers (Softpipe, LLVMpipe, Freedreno and panfrost) are also tested
   using `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__
 - Replay of application traces
 

docs/drivers/llvmpipe.rst

@@ -95,7 +95,7 @@ Environment variables
    out LLVMpipe can be fastest by using 128 bit vectors,
    yet use AVX instructions.
 ``GALLIUM_OVERRIDE_CPU_CAPS``
-   Override CPU capabilities for LLVMpipe and softpipe, possible values for x86:
+   Override CPU capabilities for LLVMpipe and Softpipe, possible values for x86:
    `nosse`
    `sse`
    `sse2`

docs/envvars.rst

@@ -521,7 +521,7 @@ Gallium environment variables
    to stderr.
 :envvar:`DRAW_FSE`
    Enable fetch-shade-emit middle-end even though its not correct (e.g.
-   for softpipe)
+   for Softpipe)
 :envvar:`DRAW_NO_FSE`
    Disable fetch-shade-emit middle-end even when it is correct
 :envvar:`DRAW_USE_LLVM`
@@ -604,10 +604,10 @@ Softpipe driver environment variables
    ``no_rast``
       rasterization is disabled. For profiling purposes.
    ``use_llvm``
-      the softpipe driver will try to use LLVM JIT for vertex
+      the Softpipe driver will try to use LLVM JIT for vertex
       shading processing.
    ``use_tgsi``
-      if set, the softpipe driver will ask to directly consume TGSI, instead
+      if set, the Softpipe driver will ask to directly consume TGSI, instead
       of NIR.
 
 LLVMpipe driver environment variables

docs/faq.rst

@@ -200,7 +200,7 @@ and then install with ``sudo ninja install``.
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If Mesa can't use its hardware accelerated drivers it falls back on one
-of its software renderers. (e.g. classic swrast, softpipe or LLVMpipe)
+of its software renderers. (e.g. classic swrast, Softpipe or LLVMpipe)
 
 You can run the ``glxinfo`` program to learn about your OpenGL library.
 Look for the ``OpenGL vendor`` and ``OpenGL renderer`` values. That will

docs/history.rst

@@ -87,7 +87,7 @@ software driver ("swr") based on LLVM and developed by Intel.
 Ongoing: Mesa is the OpenGL implementation for devices designed by
 Intel, AMD, NVIDIA, Qualcomm, Broadcom, Vivante, plus the VMware and
 VirGL virtual GPUs. There's also several software-based renderers:
-swrast (the legacy Mesa rasterizer), softpipe (a Gallium reference
+swrast (the legacy Mesa rasterizer), Softpipe (a Gallium reference
 driver) and LLVMpipe (LLVM/JIT-based high-speed rasterizer).
 
 Work continues on the drivers and core Mesa to implement newer versions

docs/osmesa.rst

@@ -14,7 +14,7 @@ information about the API functions.
 The OSMesa interface may be used with the gallium software renderers:
 
 #. LLVMpipe - this is the high-performance Gallium LLVM driver
-#. softpipe - this is the reference Gallium software driver
+#. Softpipe - this is the reference Gallium software driver
 
 There are several examples of OSMesa in the mesa/demos repository.
 

docs/releasing.rst

@@ -142,7 +142,7 @@ Regression/functionality testing
 -  *no regressions should be observed for Piglit/dEQP/CTS/Vulkan on
    Intel platforms*
 -  *no regressions should be observed for Piglit using the swrast,
-   softpipe and LLVMpipe drivers*
+   Softpipe and LLVMpipe drivers*
 
 .. _stagingbranch:
 

docs/sourcetree.rst

@@ -135,7 +135,7 @@ each directory.
          device drivers
 
          -  **clover** - OpenCL frontend
-         -  **d3d10umd** - D3D10 frontend for Windows only. It's similar to Microsoft WARP, but using LLVMpipe/softpipe.
+         -  **d3d10umd** - D3D10 frontend for Windows only. It's similar to Microsoft WARP, but using LLVMpipe/Softpipe.
          -  **dri** - Meta frontend for DRI drivers, see mesa/state_tracker
          -  **glx** - Meta frontend for GLX
          -  **hgl** - Haiku OpenGL