docs: llvmpipe -> LLVMpipe

Reviewed-by: David Heidelberg <david.heidelberg@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19191>

docs/ci/docker.rst

@@ -1,7 +1,7 @@
 Docker CI
 =========
 
-For llvmpipe and swrast CI, we run tests in a container containing
+For LLVMpipe and swrast CI, we run tests in a container containing
 VK-GL-CTS, on the shared GitLab runners provided by `freedesktop
 <http://freedesktop.org>`_
 

docs/drivers/llvmpipe.rst

@@ -4,7 +4,7 @@ LLVMpipe
 Introduction
 ------------
 
-The Gallium llvmpipe driver is a software rasterizer that uses LLVM to
+The Gallium LLVMpipe driver is a software rasterizer that uses LLVM to
 do runtime code generation. Shaders, point/line/triangle rasterization
 and vertex processing are implemented with LLVM IR which is translated
 to x86, x86-64, or ppc64le machine code. Also, the driver is
@@ -92,10 +92,10 @@ Environment variables
 
 ``LP_NATIVE_VECTOR_WIDTH``
    We can use it to override vector bits. Because sometimes it turns
-   out llvmpipe can be fastest by using 128 bit vectors,
+   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`
@@ -140,7 +140,7 @@ be used by replacing the native ICD driver, but it's quite an advanced usage, so
 you need to ask, don't even try it.
 
 There is however an easy way to replace the OpenGL software renderer
-that comes with Microsoft Windows 7 (or later) with llvmpipe (that is,
+that comes with Microsoft Windows 7 (or later) with LLVMpipe (that is,
 on systems without any OpenGL drivers):
 
 -  copy
@@ -177,7 +177,7 @@ On Linux, it is possible to have symbol resolution of JIT code with
    perf record -g /my/application
    perf report
 
-When run inside Linux perf, llvmpipe will create a
+When run inside Linux perf, LLVMpipe will create a
 ``/tmp/perf-XXXXX.map`` file with symbol address table. It also dumps
 assembly code to ``/tmp/perf-XXXXX.map.asm``, which can be used by the
 ``bin/perf-annotate-jit.py`` script to produce disassembly of the

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/gallium/debugging.rst

@@ -80,11 +80,11 @@ Dump all commands going to the hardware.
 
 .. envvar:: LP_DEBUG <flags> (0x0)
 
-Debug :ref:`flags` for the llvmpipe driver.
+Debug :ref:`flags` for the LLVMpipe driver.
 
 .. envvar:: LP_NUM_THREADS <int> (number of CPUs)
 
-Number of threads that the llvmpipe driver should use.
+Number of threads that the LLVMpipe driver should use.
 
 .. envvar:: FD_MESA_DEBUG <flags> (0x0)
 

docs/history.rst

@@ -88,7 +88,7 @@ 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
-driver) and llvmpipe (LLVM/JIT-based high-speed rasterizer).
+driver) and LLVMpipe (LLVM/JIT-based high-speed rasterizer).
 
 Work continues on the drivers and core Mesa to implement newer versions
 of the OpenGL, OpenGL ES and Vulkan specifications.

docs/osmesa.rst

@@ -13,7 +13,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
+#. LLVMpipe - this is the high-performance Gallium LLVM driver
 #. softpipe - this is the reference Gallium software driver
 
 There are several examples of OSMesa in the mesa/demos repository.
@@ -28,7 +28,7 @@ Configure and build Mesa with something like:
    meson builddir -Dosmesa=true -Dgallium-drivers=swrast -Ddri-drivers=[] -Dvulkan-drivers=[] -Dprefix=$PWD/builddir/install
    ninja -C builddir install
 
-Make sure you have LLVM installed first if you want to use the llvmpipe
+Make sure you have LLVM installed first if you want to use the LLVMpipe
 driver.
 
 When the build is complete you should find:

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,11 +135,11 @@ 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
-         -  **lavapipe** - Vulkan frontend, software Vulkan rasterizer using llvmpipe.
+         -  **lavapipe** - Vulkan frontend, software Vulkan rasterizer using LLVMpipe.
          -  **nine** - D3D9 frontend, see targets/d3dadapter9
          -  **omx** - OpenMAX Bellagio frontend
          -  **osmesa** - Off-screen OpenGL rendering library