doc:appunti:hardware:graphics_hardware_acceleration_raspberry_pi_2
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
doc:appunti:hardware:graphics_hardware_acceleration_raspberry_pi_2 [2022/10/17 12:07] – [Graphics hardware acceleration on the Raspberry Pi 2] niccolo | doc:appunti:hardware:graphics_hardware_acceleration_raspberry_pi_2 [2022/10/20 09:15] – [Enable graphics acceleration in Chromium] niccolo | ||
---|---|---|---|
Line 7: | Line 7: | ||
FIXME | FIXME | ||
- | ====== How to check if V3D and/or KMS are active | + | ===== How to check if V3D and/or KMS are active ===== |
**V3D** is an API provided by the Linux kernel to support 3D graphics on the **VideoCore VI** GPU (RPi 4). The software driver is actually provided in the form of a //Device Tree Overlay// which is loaded at boot time adding the following line into **/ | **V3D** is an API provided by the Linux kernel to support 3D graphics on the **VideoCore VI** GPU (RPi 4). The software driver is actually provided in the form of a //Device Tree Overlay// which is loaded at boot time adding the following line into **/ | ||
Line 15: | Line 15: | ||
</ | </ | ||
- | The older Raspberry Pi 3 has a **VideoCore IV** GPU and the legacy software driver was called **VC4**. The new Device Tree Overly is capable to detect the actual VideoCore available (IV or VI) and provide the same new V3D interface. | + | The older Raspberry |
To **check if V3D is enabled** you can read a ''/ | To **check if V3D is enabled** you can read a ''/ | ||
Line 29: | Line 29: | ||
</ | </ | ||
- | The KMS is instead generally | + | The **KMS** (Kernel Mode Setting) has two different implementations. The old one (known as //Fake KMS//) was the only one available at the time of Debian 9 Stretch and it is provided byt the **vc4-fkms-v3d** overlay. Once loaded |
< | < | ||
cat / | cat / | ||
</ | </ | ||
+ | |||
+ | The new overlay **vc4-kms-v3d** doesn' | ||
+ | |||
+ | < | ||
+ | cat / | ||
+ | cat / | ||
+ | cat / | ||
+ | cat / | ||
+ | cat / | ||
+ | cat / | ||
+ | </ | ||
+ | |||
+ | ===== Enable graphics acceleration in Chromium ===== | ||
+ | |||
+ | In Chromium you can open the page **%%chrome:// | ||
+ | |||
+ | ^ Canvas | ||
+ | ^ Canvas out-of-process rasterization | ||
+ | ^ Direct Rendering Display Compositor | ||
+ | ^ Compositing | ||
+ | ^ Multiple Raster Threads | ||
+ | ^ OpenGL | ||
+ | ^ Rasterization | ||
+ | ^ Raw Draw | Enabled | ||
+ | ^ Video Decode | ||
+ | ^ Video Encode | ||
+ | ^ Vulkan | ||
+ | ^ WebGL | Hardware accelerated | ||
+ | ^ WebGL2 | ||
+ | ^ WebGPU | ||
+ | |||
+ | Probably something is disabled, because of Chromium defaults. In that case you have to open the page **%%chrome:// | ||
+ | |||
+ | ^ Override software rendering list | Overrides the built-in software rendering list and enables GPU-acceleration on unsupported system configurations. | ||
+ | ^ Enable raw draw | When enabled, web content will be rastered on output surface directly. | ||
+ | ^ GPU rasterization | ||
+ | ^ Out-of-process rasterization | ||
+ | ^ Out-of-process 2D canvas rasterization | ||
+ | ^ Accelerated 2D canvas | ||
+ | ^ Hardware-accelerated video decode | ||
+ | |||
+ | |||
+ | ===== Enable graphics acceleration in Firefox ===== | ||
===== Web References ===== | ===== Web References ===== | ||
Line 40: | Line 83: | ||
* **[[https:// | * **[[https:// | ||
* **[[https:// | * **[[https:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
doc/appunti/hardware/graphics_hardware_acceleration_raspberry_pi_2.txt · Last modified: 2022/10/20 09:15 by niccolo