OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Adreno aXXX -> Adreno XXX

Browse Source 
The names of these are "Adreno XXX" or "aXXX", not "Adreno aXXX".

Reviewed-by: Yonggang Luo <luoyonggang@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19297>
This commit is contained in:
Erik Faye-Lund
2022-10-25 11:42:42 +02:00
committed by Marge Bot
parent cf0b5a60f4
commit 9fea95d907
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/drivers/freedreno/ir3-notes.rst
View File

@@ -1,7 +1,7 @@
IR3 NOTES IR3 NOTES
========= =========
Some notes about ir3, the compiler and machine-specific IR for the shader ISA introduced with Adreno a3xx. The same shader ISA is present, with some small differences, in Adreno a4xx. Some notes about ir3, the compiler and machine-specific IR for the shader ISA introduced with Adreno 3xx. The same shader ISA is present, with some small differences, in Adreno 4xx.
Compared to the previous generation a2xx ISA (ir2), the a3xx ISA is a "simple" scalar instruction set. However, the compiler is responsible, in most cases, to schedule the instructions. The hardware does not try to hide the shader core pipeline stages. For a common example, a common (cat2) ALU instruction takes four cycles, so a subsequent cat2 instruction which uses the result must have three intervening instructions (or NOPs). When operating on vec4's, typically the corresponding scalar instructions for operating on the remaining three components could typically fit. Although that results in a lot of edge cases where things fall over, like: Compared to the previous generation a2xx ISA (ir2), the a3xx ISA is a "simple" scalar instruction set. However, the compiler is responsible, in most cases, to schedule the instructions. The hardware does not try to hide the shader core pipeline stages. For a common example, a common (cat2) ALU instruction takes four cycles, so a subsequent cat2 instruction which uses the result must have three intervening instructions (or NOPs). When operating on vec4's, typically the corresponding scalar instructions for operating on the remaining three components could typically fit. Although that results in a lot of edge cases where things fall over, like:

2
docs/gallium/distro.rst
View File

@@ -56,7 +56,7 @@ Driver for the AMD Southern Islands family of GPUs.
Freedreno Freedreno
^^^^^^^^^ ^^^^^^^^^
Driver for Qualcomm Adreno a2xx, a3xx, and a4xx series of GPUs. Driver for Qualcomm Adreno 2xx, 3xx, and 4xx series of GPUs.
.. _softpipe: .. _softpipe:

2
docs/systems.rst
View File

@@ -17,7 +17,7 @@ Hardware drivers include:
`RadeonFeature <https://www.x.org/wiki/RadeonFeature>`__ `RadeonFeature <https://www.x.org/wiki/RadeonFeature>`__
- NVIDIA GPUs (GeForce 5 / FX and later). See `Nouveau - NVIDIA GPUs (GeForce 5 / FX and later). See `Nouveau
Wiki <https://nouveau.freedesktop.org>`__ Wiki <https://nouveau.freedesktop.org>`__
- Qualcomm Adreno A2xx-A6xx. See :doc:`Freedreno - Qualcomm Adreno 2xx-6xx. See :doc:`Freedreno
<drivers/freedreno>` <drivers/freedreno>`
- Broadcom VideoCore 4 and 5. See :doc:`VC4 <drivers/vc4>` and - Broadcom VideoCore 4 and 5. See :doc:`VC4 <drivers/vc4>` and
:doc:`V3D <drivers/v3d>` :doc:`V3D <drivers/v3d>`