docs: fix a bunch of typos
Saw a couple myself, and a quick round of vimspell showed a bunch more. Signed-off-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5814>
This commit is contained in:
parent
49d35f3d88
commit
9497a1fbe7
|
@ -103,7 +103,7 @@ into that pool.
|
|||
We need privileged mode and the /dev bind mount in order to get at the
|
||||
serial console and fastboot USB devices (--device arguments don't
|
||||
apply to devices that show up after container start, which is the case
|
||||
with fastboot, and the servo serial devices are acctually links to
|
||||
with fastboot, and the servo serial devices are actually links to
|
||||
/dev/pts). We use host network mode so that we can (in the future)
|
||||
spin up a server to collect XML results for fastboot.
|
||||
|
||||
|
|
|
@ -36,7 +36,7 @@ DUT requirements
|
|||
----------------
|
||||
|
||||
In addition to the general :ref:`CI-farm-expectations`, using
|
||||
docker requiers:
|
||||
docker requires:
|
||||
|
||||
* DUTs must have a stable kernel and GPU reset (if applicable).
|
||||
|
||||
|
|
|
@ -117,7 +117,7 @@ no ``parallel`` field set and:
|
|||
to just run 1/10th of the test list.
|
||||
|
||||
If a HW CI farm goes offline (network dies and all CI pipelines end up
|
||||
stalled) or its runners are consistenly spuriously failing (disk
|
||||
stalled) or its runners are consistently spuriously failing (disk
|
||||
full?), and the maintainer is not immediately available to fix the
|
||||
issue, please push through an MR disabling that farm's jobs by adding
|
||||
'.' to the front of the jobs names until the maintainer can bring
|
||||
|
@ -150,7 +150,7 @@ instead of silently reusing their container)
|
|||
|
||||
When developing a given change to your docker image, you would have to
|
||||
bump the tag on each ``git commit --amend`` to your development
|
||||
branch, which can get tedious. Instad, you can navigate to the
|
||||
branch, which can get tedious. Instead, you can navigate to the
|
||||
`container registry
|
||||
<https://gitlab.freedesktop.org/mesa/mesa/container_registry>`_ for
|
||||
your repository and delete the tag to force a rebuild. When your code
|
||||
|
|
|
@ -181,8 +181,8 @@ Core Mesa environment variables
|
|||
- This can be very useful for debugging but some features may not be
|
||||
implemented correctly. (For developers only)
|
||||
|
||||
NIR passes enviroment variables
|
||||
-------------------------------
|
||||
NIR passes environment variables
|
||||
--------------------------------
|
||||
|
||||
The following are only applicable for drivers that uses NIR, as they
|
||||
modify the behaviour for the common NIR_PASS and NIR_PASS_V macros, that
|
||||
|
@ -190,13 +190,13 @@ wrap calls to NIR lowering/optimizations.
|
|||
|
||||
``NIR_PRINT``
|
||||
If defined, the resulting NIR shader will be printed out at each
|
||||
succesful NIR lowering/optimization call.
|
||||
successful NIR lowering/optimization call.
|
||||
``NIR_TEST_CLONE``
|
||||
If defined, cloning a NIR shader would be tested at each succesful
|
||||
If defined, cloning a NIR shader would be tested at each successful
|
||||
NIR lowering/optimization call.
|
||||
``NIR_TEST_SERIALIZE``
|
||||
If defined, serialize and deserialize a NIR shader would be tested at
|
||||
each succesful NIR lowering/optimization call.
|
||||
each successful NIR lowering/optimization call.
|
||||
|
||||
Mesa Xlib driver environment variables
|
||||
--------------------------------------
|
||||
|
|
|
@ -190,7 +190,7 @@ Compiler Options
|
|||
Meson supports the common CFLAGS, CXXFLAGS, etc. environment variables
|
||||
but their use is discouraged because of the many caveats in using them.
|
||||
|
||||
Instead, it is recomended to use ``-D${lang}_args`` and
|
||||
Instead, it is recommended to use ``-D${lang}_args`` and
|
||||
``-D${lang}_link_args``. Among the benefits of these options is that
|
||||
they are guaranteed to persist across rebuilds and reconfigurations.
|
||||
|
||||
|
@ -310,7 +310,7 @@ The wrap file must define the following:
|
|||
It may also define:
|
||||
|
||||
- ``irbuilder_h``: a ``files()`` object pointing to llvm/IR/IRBuilder.h
|
||||
(this is requred for SWR)
|
||||
(this is required for SWR)
|
||||
- ``has_rtti``: a ``bool`` that declares whether LLVM was built with
|
||||
RTTI. Defaults to true
|
||||
|
||||
|
|
|
@ -30,7 +30,7 @@ somewhat dated, unfortunately.
|
|||
- **David Bucciarelli** wrote and maintained the 3Dfx Glide driver.
|
||||
Thousands of Linux/Quake players thank David!
|
||||
- **Gareth Hughes** wrote new GLU 1.2 Polygon Tessellation code (now
|
||||
superceded by SGI SI GLU).
|
||||
superseded by SGI SI GLU).
|
||||
- **Holger Waechtler** contributed AMD 3DNow! assembly code which
|
||||
accelerates vertex transformation in Mesa 3.1. Holger also
|
||||
implemented the GL_EXT_texture_env_combine extension.
|
||||
|
|
Loading…
Reference in New Issue