| Mesa | |
| Developer: | Currently: Igalia, Collabora, Valve, Intel, Google, AMD, VMware Formerly: Tungsten Graphics[1] |
| Operating System: | Cross-platform (BSDs, Haiku, Linux, etc.) |
| Genre: | Graphics library |
Mesa, also called Mesa3D and The Mesa 3D Graphics Library, is an open source implementation of OpenGL, Vulkan, and other graphics API specifications. Mesa translates these specifications to vendor-specific graphics hardware drivers.
Its most important users are two graphics drivers mostly developed and funded by Intel and AMD for their respective hardware (AMD promotes their Mesa drivers Radeon and RadeonSI over the deprecated AMD Catalyst, and Intel has only supported the Mesa driver). Proprietary graphics drivers (e.g., Nvidia GeForce driver and Catalyst) replace all of Mesa, providing their own implementation of a graphics API. An open-source effort to write a Mesa Nvidia driver called Nouveau is developed mostly by the community.
Besides 3D applications such as games, modern display servers (X.org's Glamor or Wayland's Weston) use OpenGL/EGL; therefore all graphics typically go through Mesa.
Mesa is hosted by freedesktop.org and was initiated in August 1993 by Brian Paul, who is still active in the project. Mesa was subsequently widely adopted and now contains numerous contributions from various individuals and corporations worldwide, including from the graphics hardware manufacturers of the Khronos Group that administer the OpenGL specification. For Linux, development has also been partially driven by crowdfunding.[2]
Mesa is known as housing implementations of graphic APIs. Historically the main API that Mesa has implemented is OpenGL, along with other Khronos Group related specifications (like OpenVG, OpenGL ES or recently EGL). But Mesa can implement other APIs and indeed it did with Glide (deprecated) and Direct3D 9 since July 2013.[3] Mesa is also not specific to Unix-like operating systems: on Windows for example, Mesa provides an OpenGL API over DirectX.
Mesa implements a translation layer between a graphics API such as OpenGL and the graphics hardware drivers in the operating system kernel. The supported version of the different graphic APIs depends on the driver, because each hardware driver has its own implementation (and therefore status). This is especially true for the "classic" drivers, while the Gallium3D drivers share common code that tend to homogenize the supported extensions and versions.
Mesa maintains a support matrix with the status of the current OpenGL conformance[4] [5] visualized at . Mesa 10 complies with OpenGL 3.3 for Intel, AMD/ATI, and Nvidia GPU hardware. Mesa 11 was announced with some drivers being OpenGL 4.1 compliant.[6]
Mesa 12 contains OpenGL 4.2 and 4.3 and Intel Vulkan 1.0 support.
Mesa 13 brought Intel support for OpenGL 4.4 and 4.5 (all Features supported for Intel Gen 8+, Radeon GCN, Nvidia (Fermi, Kepler), but no Khronos-Test for 4.5-Label) and experimental AMD Vulkan 1.0 support through the community driver RADV. OpenGL ES 3.2 is possible with Intel Skylake (Gen9).
1st stable version of 2017 is 17.0 (new year Counting).[7] [8] Ready features are certified OpenGL 4.5, OpenGL 4.5 for Intel Haswell,[9] [10] OpenGL 4.3 for Nvidia Maxwell and Pascal (GM107+).[11] Huge performance gain was measured with Maxwell 1 (GeForce GTX 750 Ti and more with GM1xx). Maxwell-2-Cards (GeForce GTX 980 and more with GM2xx) are underclocked without Nvidia information.[12]
The Khronos CTS test suite for OpenGL 4.4, 4.5 and OpenGL ES 3.0+ is in now (2017-01-24) Open Source and all tests for Mesa 13 and 17 are now possible without costs.[13]
2nd stable version of 2017, 17.1.0, came out on 10 May 2017 with some interesting improvements. OpenGL 4.2+ for Intel Ivy Bridge and OpenGL 3.3+ for Intel Open SWR Rasterizer are 2 of the highlights.[14] [15]
Due to the modularized nature of OpenGL, Mesa can support extensions from newer versions of OpenGL without claiming full support for such versions. For example, in July 2016, Mesa supported OpenGL ES 3.1 but also all OpenGL ES 3.2 extensions except for five, as well as a number of extensions not part of any OpenGL or OpenGL ES version.[16]
3rd Version 17.2 is available since September 2017 with some new OpenGL 4.6 features and velocity improvements in 3D for Intel and AMD. Only 1.4% of Tests fail for OpenGL 4.5 in Nouveau for Kepler.[17]
4th Version 17.3 is ready since December 2017. Many improvements in many drivers are available. OpenGL 4.6 is nearly fully available (Spir-V is not ready). AMD Vulkan Driver RADV is now fully conformant in Khronos-Test.[18]
1st version of 2018 is 18.0 and available since March 2018 by same scheme in 2017.[19] Full OpenGL 4.6 support is not ready, but many features and improvements were successfully tested in RC3. 10-bit support for Intel i965 in Colors is also a Highlight.[20] New is support for Intel Cannon Lake and AMD Vega with actual Linux Version. AMD Evergreen Chips (RV800 or R900) are near OpenGL 4.5 support. Old AMD R600 or RV700 Chips can only support OpenGL 3.3 with some features of OpenGL 4.x. Freedreno is the Driver for Adreno Hardware and near OpenGL 3.3 support.
2nd version of 2018 is 18.1 and available since May. Target is Vulkan 1.1.72 in Intel ANV and AMD RADV driver. OpenGL 4.6 with spir-V is also main target. Permanent work is possible completion of Features and Optimization of drivers for older hardware like AMD R600/Evergreen, Nvidia Tesla and before, Fermi, Kepler or Intel Sandybridge, Ivybridge, Haswell or Broadwell. ARM Architecture made also great improvements in Adreno 3xx/4xx/5xx and Broadwell VC4/VC5 for Raspi with main target OpenGL ES.
3rd version of 2018 is 18.2 and available in calendar stable in September. OpenGL 4.6 with spir-V and Vulkan 1.1.80 are in WIP. The soft Driver for virtual machines VIRGL is ready for OpenGL 4.3 and OpenGL ES 3.2. RadeonSI is also ready for OpenGL ES 3.2. ASTC Texture Compression Support and Compatibility Modus Support for OpenGL 4.4 (3.1 in 18.1) are other highlights in RadeonSI for AMD GCN Cards. New Vulkan 1.1 and more features for Intel and AMD are available. See more Details for Vulkan in Mesamatrix.[21]
4th version of 2018 is 18.3 and released as stable Version 18.3.1 in December 2018. Many features in Detail and support of newer hardware are main parts. Full support of OpenGL 4.6 is not ready.[22] [23]
1st Version of 2019 is 19.0 and was now released at March. Full support of OpenGL 4.6 is not ready, but many improvements on this way are in all drivers.[24] [25]
2nd Version of 2019 is 19.1. Transition of TGSI to NIR is here one main Feature on way to OpenGL 4.6 with Spir-V and more OpenCL. RadeonSI runs well in dev-Version with NIR.[26]
3rd Version of 2019 is 19.2. OpenGL 4.6 is Beta ready for new Intel Iris Driver.[27]
4th Version of 2019 is 19.3. OpenGL 4.6 is ready for Intel i965 and optional for new Iris Driver.[28]
First Version of 2020 is 20.0. Vulkan 1.2 is ready for AMD RADV and Intel ANV. Intel Iris is default for Intel Broadwell Gen 8+.[29] [30] RadeonSI driver switched to using NIR by default, instead of TGSI.
2nd Version of 2020 is 20.1. Many improvements are ready in many drivers. Zink is a new virtual driver for OpenGL over Vulkan.[31]
3rd Version of 2020 is 20.2. OpenGL 3.0 for Zink is one new feature. LLVMpipe will support OpenGL 4.3+ (4.5+ in 20.3). ARM Panfrost is mostly improved with many modules. Shared virtual memory is possible for OpenCL in Nouveau with Pascal and higher.[32] [33] [34]
4th Version of 2020 is 20.3. v3d and v3dv are new drivers for OpenGL and Vulkan 1.0 with Broadcom hardware like Raspberry Pi 4. OpenCL 1.2 is full supported in clover module. Zink support OpenGL 3.3+. LLVMpipe virtual driver support now OpenGL 4.5+ with 4.6 in view. Lavapipe (originally called Vallium[35]) as Vulkan Tree of LLVMpipe is merged.[36] [37] [38] [39] [40]
In Mesa 21.0 d3d12 will be merged with OpenGL 3.0 to 3.3. Microsoft and Collabora develops new emulation d3d12 in WSL2 to Windows 10 with Direct 3D 12. OpenCL 1.2 is also target in d3d12. An acceleration of factor 2 to 5 is done in Benchmark SPECviewperf with improved OpenGL Code.[41] [42] [43] [44] Many Mesa 21.0 features improves performance.[45] New Release 21.0.0 is public since 11 March 2021.
Mesa 21.1 is second release of year 2021.[46] OpenGL 4.6+ and OpenGL ES 3.1+ is available for Zink. AMD Driver 600g can change to NIR with more possibilities for old Radeon HD 5000 and 6000 cards.[47] Qualcomm Turnip reaches Vulkan 1.1+ and software emulation Lavapipe Vulkan 1.1+. Google VirtIO GPU Driver Venus with Vulkan 1.2+ is merged in experimental state with low performance in mesa main tree.[48]
Mesa 21.2 is third release of year 2021. Google Virtual Vulkan IO Driver Venus will be official introduced with full Vulkan 1.2+ support (more mesamatrix). ARM Panfrost: OpenGL ES 3.1+ Support is available and panVK is the new Vulkan Driver. Initial support started for ARM Apple M1 with new driver Asahi. 21.2 is available since 4 August 2021.[49]
An old plan is to split old drivers in a classic tree with many advantages in programming, support, bug fixing for the modern gallium 3D part. One problem here is Intel i965 with support of Popular old hardware to Intel Haswell and before also with Windows 10 support.[50] A new Gallium3D driver Crocus for Intel Gen 4 Graphics to Haswell is here in development to complete here the gallium3D area with possible split in the next time of year 2021. Crocus is optional available in 21.2.[51] Amber branch is for old drivers without Gallium 3D Functions like Radeon R200, intel i915 and 965 with actual version 21.3.9.[52]
In Version 22.0 Classic drivers are retired. Vulkan 1.3 is available for Intel Anvil and AMD RADV.[53]
Microsoft introduces new driver „Dozen“ for WSL 2 in early development stage as Vulkan over d3d12 in Mesa 22.1.[54]
RustiCL is available at 22.3 with official OpenCL 3.0 Conformance for Intel XE Graphics. Performance is equal and better to AMD ROCm with AMD 6700 XT Card.[55] [56]
A main development target of Mesa 23.0 was ray tracing for Vulkan.[57] [58]
Microsoft develops the Dozen driver for Vulkan in WSL. Vulkan 1.0+ with 80% 1.1 and 1.2 will be available in Mesa 23.2 after delay to 23.1 (See mesamatrix).[59] RustiCL for AMD hardware is available in 23.1.[60]
VirGL for virtual machines jumps in Mesa 23.2 to OpenGL 4.6.[61] Apple Asahi for Apple Arm Machines jumps from OpenGL 2.1 to 3.1 with 90% features of OpenGL 3.2 and 3.3 and OpenGL ES 2.0 to 3.0. [62]
Microsoft Supports in WSL OpenGL 4.6+ in Mesa 24.0 (in Mesa 23.3: 4.3+) with direct 12 translation driver dozen.[63]
| Mesa Version | First Release Date | Last update[64] | OpenCL ! | Direct3D | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1.3.264 2023-09-08 | 3.0 2020-11-30 | 4.6 2017-07-31 | 3.2.6 2019-07-10 | 1.1 2008-12-03 | 1.5 2014-03-19 | 1.4 2005-12-16 | 12 2015-07-29 | ||||
| 2023-05-10 | 23.1.8[65] | 1.3.244: 1.3+ (Intel Gen8+ to XE, AMD GCN Gen2+ to RDNA3, Lavapipe, Google Venus), 1.1+ (Qualcomm Turnip), 1.0+ (AMD GCN1, Broadcom v3dv, ARM Mali PanVK) | 1.0, 1.1, 1.2 (full support), 3.0 (wip, some functions in 21.1), OpenCL 1.2+ and 3.0 with new RustiCL for AMD GCN and Intel Xe (Mesa 22.3+), AMD R600, Nvidia Fermi+ (Mesa 23.1+) | 4.6 (19.3: Intel Gen 8+, 20.0: AMD GCN, 21.1: Zink, llvmpipe, 21.2: Intel Gen 7.5) | 3.2 (20.3: Intel i965, AMD radeonsi, llvmpipe, VirGL, freedreno, Zink (21.3); 3.1: AMD r600, Nvidia nvC0, softpipe, Broadcom v3d, ARM Panfrost (21.3), d3d12 (22.0) | 1.5 | 1.4 | 9.0c[66] [67] | |||
| 2023-02-23 | 23.0.4[68] | 1.3.232: mostly equal to 23.1 | |||||||||
| 2022-11-30 | 22.3.7[69] | 22.3: 1.3.225: 1.3+ (Intel Gen8+, AMD GCN Gen2+, Lavapipe), 1.2+ (Google Venus), 1.1+ (Qualcomm Turnip, Lavapipe (22.2)), 1.0+ (AMD GCN1, Broadcom v3dv, ARM Mali PanVK) | |||||||||
| 2022-09-21 | 22.2.5[70] | ||||||||||
| 2022-05-20 | 22.1.7[71] | ||||||||||
| 2022-03-09 | 22.0.5[72] | ||||||||||
| 2021-11-17 | 21.3.9[73] | 21.3: 1.2.190 (Intel Gen8+, AMD GCN Gen2+, Google Venus (21.3), Lavapipe), 1.0+ (AMD GCN1, Broadcom v3dv), 1.1+ (Qualcomm Turnip, Lavapipe (21.1)) | |||||||||
| 2021-08-04 | 21.2.6[74] | ||||||||||
| 2021-05-05 | 21.1.8[75] | ||||||||||
| 2021-03-11 | 21.0.3[76] | ||||||||||
| 2020-12-03 | 20.3.5[77] | 20.3: 1.2.158 (Intel Gen8+, AMD GCN Gen2+), 1.0+ (AMD GCN1, Broadcom v3dv (20.3)) | |||||||||
| 2020-09-28 | 20.2.6[78] | 1.0, 1.1, 1.2 (WIP) some failed conformance tests | |||||||||
| 2020-05-27 | 20.1.10 | ||||||||||
| 2020-02-19 | 20.0.8[79] | 1.2+ (Intel Gen8+, AMD GCN Gen2+) | |||||||||
| 2019-12-11 | 19.3.5[80] [81] | 1.1+ (Intel Gen8+, AMD GCN Gen2+) (19.1: 1.1.104 19.0: 1.1.102, 18.3: 1.1.90, 18.2: 1.1.84) | |||||||||
| 2019-09-25 | 19.2.8 | 4.5 | |||||||||
| 2019-06-11 | 19.1.8 | ||||||||||
| 2019-03-13 | 19.0.8 | ||||||||||
| 2018-12-07 | 18.3.6 | ||||||||||
| 2018-09-07 | 18.2.8 | ||||||||||
| 2018-05-18 | 18.1.9[82] | 1.1 (Intel Gen8+, AMD GCN Gen2+)(1.1.73) | |||||||||
| 2018-03-27 | 18.0.5 | 1.0+ (1.0.66) | |||||||||
| 2017-12-08 | 17.3.9 | 1.0 (PC: ANV Intel Gen7+ Ivy Bridge, RADV AMD GCN only) (header: 17.3: 1.0.63, 17.2: 1.0.54, 17.1: 1.0.42, 17.0: 1.0.38, 13.0: 1.0.6, 12.0: 1.0.3) | in dev. by Gallium Compute (Clover): some CTS-Tests fail in 1.0 and 1.1, 1.2 (WIP), so 1.0, 1.1, 1.2 incomplete[83] [84] | ||||||||
| 2017-09-04 | 17.2.8 | ||||||||||
| 2017-05-10 | 17.1.10 | ||||||||||
| 17.0.7 | |||||||||||
| 2016-11-01[85] | 13.0.6 | 4.4 (4.5 No Test Label) | |||||||||
| 2016-07-08 | 12.0.6 | 4.3[86] | 3.1 | ||||||||
| 2016-04-04[87] | 11.2.2 | rowspan="19" | 4.1 (Intel 3.3+) | ||||||||
| 2015-12-15[88] | 11.1.4 | 3.0 | |||||||||
| 2015-09-12[89] | 11.0.9 | ||||||||||
| 2015-06-15[90] | 10.6.9 | 3.3[91] | 1.4 | ||||||||
| 2015-03-06[92] | 10.5.9 | 1.1 | |||||||||
| 2014-12-14[93] | 10.4.7 | ||||||||||
| 2014-09-19[94] | 10.3.7 | rowspan="13" | |||||||||
| 2014-06-06[95] | 10.2.9 | ||||||||||
| 2014-03-04[96] | 10.1.6 | ||||||||||
| 2013-11-30[97] | 10.0.5 | ||||||||||
| 2012-10-08 | 9.0.3, 9.1.7, 9.2.5 | rowspan="9" | 3.1 | 2.0 | |||||||
| 2012-02-08 | 8.0.5 | 3.0 | |||||||||
| 2007-06-22 | 7.0.4, ..., 7.11.2 | 2.1 | rowspan="7" | rowspan="7" | rowspan="7" | ||||||
| 2004-01-06 | 6.0.1 | 1.5 | 1.3 | ||||||||
| 2002-11-13 | 5.0.2 | 1.4 | |||||||||
| 2001-10-22 | 4.0.4 | 1.3 | |||||||||
| 1998-09 | 3.1, 3.2.1, 3.4.2.1 | 1.2 | |||||||||
| 1996-10 | 2.6 | 1.1 | |||||||||
| 1995-02 | 1.2.8 | 1.0 | |||||||||
The Khronos Group officially announced Vulkan API in March 2015, and officially released Vulkan 1.0 on 16 February 2016. Vulkan breaks compatibility with OpenGL and completely abandons its monolithic state machine concept. The developers of Gallium3D called Vulkan to be something along the lines of Gallium3D 2.0 – Gallium3D separates the code that implements the OpenGL state machine from the code that is specific to the hardware.
Version 1.3 is immediately available with Mesa 22.0. Hardware with support of OpenGL ES 3.1 should run at Vulkan Level 1.3 and before.[98]
As Gallium3D ingests TGSI, Vulkan ingests SPIR-V (Standard Portable Intermediate Representation version "V" as in "Vulkan").
Intel released their implementation of a Vulkan driver for their hardware the day the specification was officially released, but it was only mainlined in April and so became part of Mesa 12.0, released in July 2016. While already the i965 driver wasn't written according to the Gallium3D specifications, for the Vulkan driver it makes even less sense to flange it on top of Gallium3D. Similarly there is no technical reason to flange it with NIR, but yet Intel's employees implemented their Vulkan driver that way.[99]
It is to be expected that AMD's own proprietary Vulkan driver, which was released in March, and was announced to be released as free and open-source software in the future and be mainlined into Mesa, also abandons Gallium3D.[100]
RADV is a free project for AMD and is available since version 13.[101] Conformance with Khronos-Test came in version 17.3. Actual is Full support of Vulkan 1.0 and 1.1 since Mesa 18.1.
Nvidia released their proprietary GeForce driver with Vulkan support at launch day and Imagination Technologies (PowerVR), Qualcomm (Adreno) and ARM (Mali) have done the same or at least announced proprietary Vulkan drivers for Android and other operating systems. But when and whether additional free and open-source Vulkan implementations for these GPUs will show up, remains to be seen.
Mesa Software Driver VIRGL starts Vulkan Development in 2018 with GSOC projects for support of Virtual machines.[102]
Lavapipe is a CPU-based Software Vulkan driver and the brother of LLVMpipe. Mesa Version 21.1 supports Vulkan 1.1+.[103]
Google introduces Venus Vulkan Driver for virtual machines in Mesa 21.1 with full support for Vulkan 1.2+.[48]
Qualcomm Turnip and Broadcom v3dv are new drivers for Qualcomm Adreno and Broadcom Raspberry 4 Hardware. Turnip is the Vulkan brother of freedreno for OpenGL. V3dv supports Vulkan 1.0+ since Mesa 20.3. In Version 21.1 Turnip supports Vulkan 1.1+.[104] [105] [106]
Panfrost PanVK for ARM Mali is at way to Vulkan 1.1, but only 1.0 is stable available with Mesa 22.0.[107]
Project Dozen is connecting direct 3D 12 (d3d12) with Vulkan for Linux Emulation WSL2 in Windows 10 and 11. In Mesa 23.2 Vulkan 1.0 is full conformant supported and 80% of 1.1 and 1.2 (mesamatrix). [108] [109]
A kind of memory barrier that separates one buffer from the rest of the memory is called a fence. Fences are there to ensure that a buffer is not being overwritten before rendering and display operations have completed on it. Implicit fencing is used for synchronization between graphics drivers and the GPU hardware. The fence signals when a buffer is no longer being used by one component so it can be operated on or reused by another. In the past the Linux kernel had an implicit fencing mechanism, where a fence is directly attached to a buffer (cf. GEM handles and FDs), but userspace is unaware of this. Explicit fencing exposes fences to userspace, where userspace gets fences from both the Direct Rendering Manager (DRM) subsystem and from the GPU. Explicit fencing is required by Vulkan and offers advantages for tracing and debugging.
Linux kernel 4.9 added Android's synchronization framework to mainline.[110]
Generic Buffer Management (GBM) is an API that provides a mechanism for allocating buffers for graphics rendering tied to Mesa. GBM is intended to be used as a native platform for EGL on DRM or openwfd. The handle it creates can be used to initialize EGL and to create render target buffers.[111]
Mesa GBM is an abstraction of the graphics driver specific buffer management APIs (for instance the various libdrm_* libraries), implemented internally by calling into the Mesa GPU drivers.
For example, the Wayland compositor Weston does its rendering using OpenGL ES 2, which it initializes by calling EGL. Since the server runs on the "bare KMS driver", it uses the EGL DRM platform, which could really be called the GBM platform, since it relies on the Mesa GBM interface.
At XDC2014, Nvidia employee Andy Ritger proposed to enhance EGL in order to replace GBM.[112] This was not taken positively by the community, and Nvidia eventually changed their mind,[113] and took another approach.
There are three possible ways to do the calculations necessary for the encoding and decoding of video streams:
For example, Nouveau, which has been developed as part of Mesa, but also includes a Linux kernel component, which is being developed as part of the Linux kernel, supports the PureVideo-branded ASICs and provides access to them through VDPAU and partly through XvMC.[114]
The free radeon driver supports Unified Video Decoder and Video Coding Engine through VDPAU and OpenMAX.[115]
V4L2 is a kernel-to-user-space interface for video bit streams delivered by webcams or TV tuners.
Due to patent concerns regarding the H.264, H.265 and VC-1 video codecs, Fedora Linux disabled support for VAAPI acceleration for those in its build of Mesa in September 2022.[116]
See main article: Free and open-source graphics device driver. The available free and open-source device drivers for graphic chipsets are "stewarded" by Mesa (because the existing free and open-source implementation of APIs are developed inside of Mesa). Currently there are two frameworks to write graphics drivers: "classic" and Gallium3D.[117] An overview over some (but not all) of the drivers available in Mesa is given at .
There are device drivers for AMD/ATI R100 to R800, Intel, and Nvidia cards with 3D acceleration. Previously drivers existed for the IBM/Toshiba/Sony Cell processor of the PlayStation 3, S3 Virge & Savage chipsets, VIA chipsets, Matrox G200 & G400, and more.[118]
The free and open-source drivers compete with proprietary closed-source drivers. Depending on the availability of hardware documentation and man-power, the free and open-source driver lag behind more or less in supporting 3D acceleration of new hardware. Also, 3D rendering performance was usually significantly slower with some notable exceptions.[119] [120] [121] [122] Today this is still true for Nouveau for most NVIDIA GPUs while on AMDs Radeon GPUs the open driver now mostly matches or exceeds the proprietary driver's performance.
See main article: Direct Rendering Infrastructure.
At the time 3D graphics cards became more mainstream for PCs, individuals partly supported by some companies began working on adding more support for hardware-accelerated 3D rendering to Mesa. The Direct Rendering Infrastructure (DRI) was one of these approaches to interface Mesa, OpenGL and other 3D rendering API libraries with the device drivers and hardware. After reaching a basic level of usability, DRI support was officially added to Mesa. This significantly broadened the available range of hardware support achievable when using the Mesa library.
With adapting to DRI, the Mesa library finally took over the role of the front end component of a full scale OpenGL framework with varying backend components that could offer different degrees of 3D hardware support while not dropping the full software rendering capability. The total system used many different software components.
While the design requires all these components to interact carefully, the interfaces between them are relatively fixed. Nonetheless, as most components interacting with the Mesa stack are open source, experimental work is often done through altering several components at once as well as the interfaces between them. If such experiments prove successful, they can be incorporated into the next major or minor release. That applies e.g. to the update of the DRI specification developed in the 2007-2008 timeframe. The result of this experimentation, DRI2, operates without locks and with improved back buffer support. For this, a special git branch of Mesa was created.[123]
DRI3 is supported by the Intel driver since 2013[124] [125] and is default in some Linux distributions since 2016[126] to enable Vulkan support and more. It is also default on AMD hardware since late 2016 (X.Org Server 1.18.3 and newer).[127]
Mesa also contains an implementation of software rendering called that allows shaders to run on the CPU as a fallback when no graphics hardware accelerators are present. The Gallium software rasterizer is known as softpipe or when built with support for LLVM llvmpipe, which generates CPU code at runtime.[128] [129] Since Mesa 10.x OpenGL 3.3+ is supported for Softpipe (10.3) and LLVMpipe (10.2). Actually about 80% of Features from OpenGL 4.x are implemented in Mesa 17.3 (See Mesamatrix).
In Mesa 12.0 a new Intel Rasterizer OpenSWR is available with high advantages in clusters for large data sets. It's more focused on engineering visualisation than in game or art imagery and can only work on x86 processors.[130] On the other hand, OpenGL 3.1+ is now supported.[131] Acceleration values from 29 to 51 related to LLVMPIPE were measured in some examples.[132] OpenGL 3.3+ is supported for OpenSWR since Mesa 17.1.
VirGL is a Rasterizer for Virtual machines implemented in Mesa 11.1 since 2015 with OpenGL 3.3 support and showed in Mesamatrix since Mesa 18. In actual new Mesa 18.2 it supports more than the others with OpenGL 4.3 and OpenGL ES 3.2. About 80% of OpenGL 4.4 and 4.5 features are also now ready. Vulkan Development starts with GSOC 2018 projects.[133] [134] [135] [102] [136] [137] [138]
Actual virGL state in Mesamatrix is full support of OpenGL 4.6+ and OpenGL ES 3.2+ with some necessary Linux software.[139]
D3d12 is a project of Microsoft for WSL2 emulation of OpenGL 3.3+ and OpenCL 1.2+ with Direct3D 12. D3D12 is merged in 21.0.[41] Actual state in Mesa 23.1 is OpenGL 4.2+ with nearly 4.4+ and OpenGL ES 3.1+.
Venus is a new Vulkan VirtIO GPU Driver for GPU in virtual machines by Google. Venus is merged in 21.1 and for public in 21.2 introduced.[48] Venus supports Vulkan 1.3+ in Mesa 23.1. Hardware minimum is Vulkan 1.1 with some extensions.[140]
The idea of bundling multiple drivers into a single "mega" driver was proposed by Emma Anholt. It allows for a single copy of the shared Mesa code to be used among multiple drivers (instead of it existing in each driver separately) and offering better performance than a separate shared library due to the removal of the internal library interface.[141] The state trackers for VDPAU and XvMC have become separate libraries.[142]
shader-db is a collection of about 20,000 shaders gathered from various computer games and benchmarks as well as some scripts to compile these and collect some statistics. Shader-db is intended to help validate an optimization.
It was noticed that an unexpected number of shaders are not hand-written but generated. This means these shaders were originally written in HLSL and then translated into GLSL by some translator program, such as e.g. HLSL2GLSL. The problem is, that the generated code is often far from being optimal. Matt Turner said it was much easier to fix this in the translator program than having to make Mesa's compiler carry the burden of dealing with such bloated shaders.
shader-db cannot be considered free and open-source software. To use it legally, one must have a license for all the computer games that the shaders are part of.
The so-called "user-mode graphics device drivers" (UMD) in Mesa have very few commonalities with what is generally called a device driver. There are a couple of differences:
/drivers/gpu/drm/ Each UMD communicates with its kernel mode counterpart with the help of a specific library, name libdrm_specific and a generic one, named libdrm. This section shall look solely on the user-mode part above libdrmOne goal of Mesa is the optimization of code that is to be executed by the respective GPU. Another is the sharing of code. Instead of documenting the pieces of software, this article shall instead look at the Intermediate Representations used in the process of compiling and optimizing. See Abstract syntax tree (AST) and Static single assignment form (SSA form).
SPIR-V is a certain version of the Standard Portable Intermediate Representation. The idea is, that graphics applications output SPIR-V instead of GLSL. In contrast to the latter, SPIR-V is binary to avoid implementation differences between GLSL compiler frontends of different driver implementations, as this has been a major source of application incompatibilities and bugs. Also SPIR-V binary usually also passed through some general optimizations. SPIR-V's binary representation also offers some degree of obfuscation, which might appeal to some software vendors as a form of intellectual property protection; however, SPIR-V contains ample information for reflection and tools exist that translate SPIR-V back into high quality, human readable high level code. A UMD needs only apply optimizations, that are specific to the supported hardware.
NIR (New Internal Representation) was introduced to overcome TGSI limitations.[143] [144] NIR was extended in last and actual releases as base of Spir-V support and is since 2016 main development area. LLVMpipe, i965, RadeonSI, Nouveau, freedreno, vc4 are changed to NIR from TGSI. RADV, Zink and other new drivers starts with NIR. All drivers with full OpenGL 4.6 support are related to NIR by SPIR-V support. Also AMD r600 has a fork with NIR for better support of HD5000 and HD6000 series. This option for r600 is default since Mesa 21.0.
The Tungsten Graphics Shader Infrastructure (TGSI) was introduced in 2008 by Tungsten Graphics. All Gallium3D-style UMDs ingest TGSI.NIR is now Main development area, so TGSI is only for older driver like r300g default infrastructure and will be deprecated in some years.
GLSL-To-TGSI code will be deleted in Mesa 22.2. Default is newer NIR-to-TGSI with GLSL-to-NIR for all native NIR drivers. Some older TGSI drivers are supported with this NIR Code path. Later NIR-To-TGSI will be deprecated for native NIR drivers only.[145]
The UMDs radeonsi and llvmpipe do not output machine code, but instead LLVM IR. From here on, LLVM does optimizations and the compilation to machine code. This does mean, that a certain minimum version of LLVM has to be installed as well.
RADV ACO uses own IR that is close to NIR, for optimizing and generating end binary code for Vulkan SPIR-V shaders on top of Radeon GPUs (GCN 1+, aka GFX6+) GPUs. As of version 20.1.0 the ACO is only used in RADV (Vulkan driver) and not in RadeonSI yet.
Mesa's GLSL compiler generates its own IR. Because each driver has very different requirements from a LIR, it differentiates between HIR (high-level IR) and LIR (low-level IR).
| Gallium3D | |
| Author: | Tungsten Graphics (now VMware) |
| Latest Preview Version: | 0.4[146] |
| Operating System: | Cross-platform |
| Genre: | Graphics library |
| License: | MIT License |
Gallium3D is a set of interfaces and a collection of supporting libraries[147] intended to ease the programming of device drivers for 3D graphics chipsets for multiple operating systems, rendering or video acceleration APIs. It is free and open-source graphics device driver software.
A feature matrix is being provided at .
The development of Gallium3D started in 2008 at Tungsten Graphics,[148] and the implementation is available as free and open-source software as part of Mesa 3D hosted by freedesktop.org. The primary goal of making driver development easier, bundling otherwise duplicated code of several different drivers at a single point, and to support modern hardware architectures. This is done by providing a better division of labor, for example, leaving memory management to the kernel DRI driver.
Gallium3D has been a part of Mesa since 2009[149] and is currently used by the free and open-source graphics driver for Nvidia (nouveau project),[150] [151] for AMD's R300–R900,[152] [153] [154] Intel's 'Iris' driver for generation 8+ iGPUs[155] and for other free and open-source GPU device drivers.
Gallium3D eases programming of device drivers by splitting the graphics device driver into three parts. This is accomplished by the introduction of two interfaces: Gallium3D State Tracker Interface and the Gallium3D WinSys Interface. The three components are called:
Gallium3D provides a unified API exposing standard hardware functions, such as shader units found on modern hardware. Thus, 3D APIs such as OpenGL 1.x/2.x, OpenGL 3.x, OpenVG, GPGPU infrastructure or even Direct3D (as found in the Wine compatibility layer) will need only a single back-end, called a state tracker, targeting the Gallium3D API. By contrast, classic-style DRI device drivers require a different back-end for each hardware platform and several other APIs need translation to OpenGL at the expense of code duplication.[156] [157] [158] All vendor device drivers, due to their proprietary and closed-source nature, are written that way meaning that, e.g. the AMD Catalyst implements both OpenGL and Direct3D, and the vendor drivers for the GeForce have their implementations.
Under Gallium3D, Direct Rendering Manager (DRM) kernel drivers will manage the memory and Direct Rendering Interface (DRI2) drivers will be more GPU processing oriented.[159] During the transition period from userspace modesetting to kernelspace modesetting some of the Mesa 3D drivers, such as the radeon driver or Intel's drivers, ended up supporting both DRI1 and DRI2 and used DRI2 if available on the system. Gallium3D additionally requires a level of shader support that is not available on older cards like e.g. ATi r100-r200 so users for those cards need to keep using Mesa 3D with DRI2 for their 3D usage.
Tungsten Graphics Shader Infrastructure (TGSI) is an Intermediate representation like LLVM Intermediate Representation or the new Standard Portable Intermediate Representation (SPIR) to be used by the Vulkan API and OpenCL 2.1. Shaders written in OpenGL Shading Language are to be translated/compiled into TGSI, then optimizations are made, and then the TGSI shaders are being compiled into shaders for the instruction set of the used GPU.
NIR is the new Layer representation in Mesa with full SPIR-V support and since 2019 main development area of all newer drivers with OpenGL 4.6 support.
In addition, using the modular structure of Gallium3D, there is an effort underway to use the LLVM compiler suite and create a module to optimize shader code on the fly.[160]
The library represents each shader program using an extensible binary intermediate representation called Tungsten Graphics Shader Infrastructure (TGSI), which LLVM then translates into GLSL shaders optimized for target hardware.
Several free and open-source graphics device drivers, which have been, or are being written based on information gained through clean-room reverse engineering, adopted the driver model provided by Gallium3D, e.g. nouveau and others (see Free and open-source graphics device driver for a complete list). The main reason may be that the Gallium3D driver model lessens the amount of code required to be written. Of course, being licensed under a free software license, this code can at any time by anybody be rewritten to implement the DRI-, or some other, driver model.
Original authors of Gallium3D were Keith Whitwell and Brian Paul at Tungsten Graphics (acquired by VMware in 2008).[161]
As of fall 2011, there were at least 10 known, mature and working Gallium3D drivers.[162] Open-source drivers for Nvidia graphics cards by the name of Nouveau team develops its drivers using the Gallium3D framework.[163]
2008-07-13: Nouveau development is done exclusively for the Gallium framework. The old DRI driver was removed from the master branch of the Mesa repository on Freedesktop.org.[164]
2009-02-11: The gallium-0.2 branch was merged into mainline Master branch of Mesa.[165] Development is done in Mesa mainline.
2009-02-25: Gallium3D can run on Linux as well as FreeBSD kernels.[166]
2009-05-01: Zack Rusin from Tungsten Graphics added the OpenVG state tracker to Mesa 3D,[167] which enables Scalable Vector Graphics to be hardware-accelerated by any Gallium3D-based driver.
2009-07-17: Mesa3D 7.5 is released, the first version to include Gallium3D.[168]
2010-09-10: Initial support for the Evergreen GPUs was added to the r600g driver.[169]
2010-09-21: There are two Gallium3D drivers for ATI hardware known as r300g and r600g for R300-R500 and R600-Evergreen GPUs respectively.
2010-09-21: Major commits were made to the code to support Direct3D 10 and 11.[170] In time, this might offer the ability to use recent Direct3D implementations on Linux systems.
2011-11-30: Intel 965g and Cell Gallium drivers were removed from the master branch of Mesa as unmaintained and broken.[171] [172]
2013-11-30: Mesa 10 with OpenGL 3.2, 3.3 and OpenCL 1.0+
2014-11-18: Major commits were made to the code to support Direct3D 9.[173]
2015-09-15: Mesa 11 with OpenGL 4.0, 4.1 and OpenCL 1.2 (incomplete)
2015-12-15: Mesa 11.1 Driver VIRGL for virtual machines with OpenGL 3.3
2016-07-08: Mesa 12 with OpenGL 4.2, 4.3 and Vulkan 1.0 (Intel ANV and AMD RADV)
2016-11-01: Mesa 13 with OpenGL 4.4 and OpenGL ES 3.2
2017-02-13: Mesa 17.0 with OpenGL 4.5 and freedreno driver with OpenGL 3.0 and 3.1
2017-05-10: Mesa 17.1 OpenGL 4.2+ for Intel Ivy Bridge (more than Intel driver for Windows, OpenGL 3.3+ for Intel Open SWR Rasterizer (important for cluster Computer for huge simulations)
2017-12-08: Mesa 17.3 AMD Vulkan Driver RADV full compliant in Khronos Test of Vulkan 1.0
2018-05-18: Mesa 18.1 with Vulkan 1.1 (Intel ANV and AMD RADV)
2018-09-07: Mesa 18.2 with OpenGL 4.3 for Soft Driver VIRGL (important for virtual machines in cloud Cluster Computer), OpenGL ES 3.1 for Freedreno with Adreno A5xx
2019-06-11: Mesa 19.1 released with Intel's next generation 'iris' graphics driver for generation 8+ iGPUs[174]
2019-12-11: Mesa 19.3 released OpenGL 4.6 with Intel i965 with gen 7+ and optional Iris Gen 8+
2020-03-18: Mesa 20.0 released OpenGL 4.6 with AMD GCN and Vulkan 1.2 for Intel
2020-05-27: Mesa 20.1 released NIR vectorisation support and shared virtual memory support for OpenCL in Clover
2020-11-30: Mesa 20.3 full support of OpenCL 1.2 in Clover[37]
2021-03-11: Mesa 21.0 initial support of "D3D12“: Direct 3D 12 for WSL2 in Windows 10 with OpenGL 3.3+, ARM Freedreno: OpenGL 3.3+
2021-05-05: Mesa 21.1 initial support of Google VirtIO GPU Driver "Venus“ with Vulkan 1.2+; Zink: OpenGL 4.6+, OpenGL ES 3.1+; Qualcomm Turnip, Lavapipe: Vulkan 1.1+
2021-08-04: Mesa 21.2 initial support of new Intel Crocus OpenGL 4.6 driver based on gallium3D to Intel Sandy Bridge to Haswell for old i965, Vulkan Driver panVK for ARM Panfrost
2022-03-09: Mesa 22.0 full support of Vulkan 1.3 by Intel Anvil and AMD RADV
2023-05-10: Mesa 23.1 OpenCL with Rust: RustiCL for AMD GCN Hardware available (more hardware wip)[175]
2023-09-30: Mesa 23.2 with Apple Asahi OpenGL 3.1 and OpenGL ES 3.0, RADV supports Ray Tracing in AMD RDNA 2 and 3, Intel Anvil Vulkan H.265 decoding support [176]
Project initiator Brian Paul was a graphics hobbyist. He thought it would be fun to implement a simple 3D graphics library using the OpenGL API, which he might then use instead of VOGL (very ordinary GL Like Library).[177] Beginning in 1993, he spent eighteen months of part-time development before he released the software on the Internet in February 1995.[178] The software was well received, and people began contributing to its development. Mesa started off by rendering all 3D computer graphics on the CPU. Despite this, the internal architecture of Mesa was designed to be open for attaching to graphics processor-accelerated 3D rendering. In this first phase, rendering was done indirectly in the display server, leaving some overhead and noticeable speed lagging behind the theoretical maximum. The Diamond Monster 3D, using the Voodoo Graphics chipset, was one of the first 3D hardware devices supported by Mesa.
The first true graphics hardware support was added to Mesa in 1997, based upon the Glide API for the then new 3dfx Voodoo I/II graphics cards and their successors.[179] A major problem of using Glide as the acceleration layer was the habit of Glide to run full screen, which was only suitable for computer games. Further, Glide took the lock of the screen memory, and thus the display server was blocked from doing any other GUI tasks.[180]