fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2025-12-20 13:50:11 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

docs/v3d: update v3d documentation

Browse source 
In order to include a reference to the Raspberry Pi 5, and that the
support for 3.3 and 4.1 got dropped.

Acked-by: Emma Anholt <emma@anholt.net>
Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25851>
This commit is contained in:
Alejandro Piñeiro 2023-10-31 23:36:48 +01:00
parent 87a673cac4
commit b509446c2c
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/drivers/v3d.rst
View file

@ -5,22 +5,25 @@ Mesa's V3D graphics driver stack includes a `conformant GLES3.1
driver driver
<https://www.khronos.org/conformance/adopters/conformant-products/opengles#submission_882>`__ <https://www.khronos.org/conformance/adopters/conformant-products/opengles#submission_882>`__
called V3D and a Vulkan graphics driver called V3DV, notably called V3D and a Vulkan graphics driver called V3DV, notably
used on the Raspberry Pi 4. used on the Raspberry Pi 4 and Raspberry Pi 5.
The V3D Mesa drivers communicate directly with the `V3D The V3D Mesa drivers communicate directly with the `V3D
<https://www.kernel.org/doc/html/latest/gpu/v3d.html>`__ kernel DRM <https://www.kernel.org/doc/html/latest/gpu/v3d.html>`__ kernel DRM
driver for scheduling GPU commands. Additionally, on the Raspberry Pi driver for scheduling GPU commands. Additionally, on the Raspberry Pi
4, the kernel uses the VC4 DRM driver for display support, so Mesa 4 and 5, the kernel uses the VC4 DRM driver for display support, so Mesa
exposes a ``vc4_dri.so`` using the kmsro helpers to do exposes a ``vc4_dri.so`` using the kmsro helpers to do
behind-the-scenes buffer management between the two kernel drivers, behind-the-scenes buffer management between the two kernel drivers,
while executing rendering on the V3D kernel module. while executing rendering on the V3D kernel module.
Initial development work was done on the Broadcom 7268 (V3D 3.3) and Initial development work was done on the Broadcom 7268 (V3D 3.3) and
7278 (V3D 4.1). Development since then has been on V3D 4.2, and 7278 (V3D 4.1). Development since then has been on V3D 4.2 (Raspberry
though the 3.3 and 4.1 support continues to remain in tree, it is not Pi 4), and V3D 7.1 (Raspberry Pi 5). When the support for V3D 7.1
tested any more. Broadcom's reference software platforms do not make landed, the support for 3.3 and 4.1 was dropped as it was not tested
use of the open source V3D stack, but porting a particular hardware anymore (see `MR#25851
implementation to use it would still be possible. <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25851>`__)
Broadcom's reference software platforms do not make use of the open
source V3D stack, but porting a particular hardware implementation to
use it would still be possible.
Hardware Documentation Hardware Documentation
---------------------- ----------------------