From eff5d950ea894cc91442f59c052c9eff04574136 Mon Sep 17 00:00:00 2001 From: Harri Nieminen Date: Mon, 27 Mar 2023 22:13:50 +0300 Subject: [PATCH] docs/freedreno: Fix typos Found by codespell Part-of: --- docs/drivers/freedreno.rst | 6 +++--- docs/drivers/freedreno/isaspec.rst | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/drivers/freedreno.rst b/docs/drivers/freedreno.rst index 26c0703d383..0922344535f 100644 --- a/docs/drivers/freedreno.rst +++ b/docs/drivers/freedreno.rst @@ -79,7 +79,7 @@ Hardware acronyms Visibility Stream Compressor PVS - Primitive Visibiliy Stream + Primitive Visibility Stream FE Front End? Index buffer and vertex attribute fetch cluster. Includes PC, @@ -264,7 +264,7 @@ SSBOs are just untyped buffers, but otherwise use the same descriptors and instructions as images. Samplers use a 16byte descriptor, and UBOs use an 8byte descriptor which packs the size in the upper 15 bits of the UBO address. -In the bindless model, descriptors are split into 5 desciptor sets, which are +In the bindless model, descriptors are split into 5 descriptor sets, which are global across shader stages (but as with bindful IBO descriptors, separate for 3d stages vs compute stage). Each hw descriptor is an array of descriptors of configurable size (each descriptor set can be configured for a descriptor @@ -609,7 +609,7 @@ the cases where stale data is read. stomp registers before each renderpass. ``inverse`` changes `TU_DEBUG_STALE_REGS_RANGE` meaning to - "regs that should NOT be stompted". + "regs that should NOT be stomped". The best way to pinpoint the reg which causes a failure is to bisect the regs range. In case when a fail is caused by combination of several registers diff --git a/docs/drivers/freedreno/isaspec.rst b/docs/drivers/freedreno/isaspec.rst index 2c1866afaed..b87dfaf0e74 100644 --- a/docs/drivers/freedreno/isaspec.rst +++ b/docs/drivers/freedreno/isaspec.rst @@ -201,7 +201,7 @@ Overrides In many cases, a bitset is not convenient for describing the expected disasm syntax, and/or interpretation of some range of bits differs based on some other field or combination of fields. These *could* be modeled -as different derived bitsets, at the expense of a combinatorical explosion +as different derived bitsets, at the expense of a combinatorial explosion of the size of the bitset inheritance tree. For example, *every* cat2 (and cat3) instruction has both a ``(nopN)`` interpretation in addition to the ``(rptN`)`` interpretation.