Initial - But Disabled - Support Added For Intel Meteor Lake With Mesa 23.0
Intel engineers have been busy bringing up Meteor Lake support for Linux from the improved integrated graphics to other areas of this next-gen Core processor that will eventually succeed Raptor Lake. In addition to heavy and ongoing work with the i915 kernel graphics driver, the initial Meteor Lake support has been merged now for Mesa.
The initial device information / platform for Meteor Lake (MTL) has been merged to Mesa 23.0. However, this preliminary support is disabled by default: the PCI IDs are commented out so one would need to recompile Mesa with those lines un-commented to enjoy any support. For right now this Mesa code is just the bare enablement with much of the focus currently being on the kernel graphics driver side and building off the existing DG2 driver code paths.
This disabled support is similar to what Intel engineers did when bringing up DG2/Alchemist Arc Graphics is leaving the PCI IDs commented out until ready to treat the OpenGL and Vulkan driver support as stable/supported.
The added but disabled Meteor Lake graphics IDs are 0x7d40, 0x7d45, 0x7d55, 0x7d60, and 0x7dd5. Ther Meteor Lake device information reaffirms that is already known for the integrated graphics is that they will be close to what is found with DG2/Alchemist discrete graphics hardware but in integrated form -- including features like Vulkan mesh shaders and ray-tracing to work with Meteor Lake integrated graphics.
So this patch is now part of Mesa 23.0 but don't expect the support to be enabled/advertised until a later release once ensuring the user-space API and all functionality is in good shape. Similarly, as of Linux 6.2 / DRM-Next the Meteor Lake support is still treated as experimental / behind the "force_probe" option.
Meteor Lake processors aren't expected to be released until late 2023 or even 2024 with there already being delay rumors. In which case there still are a few Linux kernel and Mesa releases to go where this new code can get squared away before enabling it and still having out-of-the-box support in time for launch day.
The initial device information / platform for Meteor Lake (MTL) has been merged to Mesa 23.0. However, this preliminary support is disabled by default: the PCI IDs are commented out so one would need to recompile Mesa with those lines un-commented to enjoy any support. For right now this Mesa code is just the bare enablement with much of the focus currently being on the kernel graphics driver side and building off the existing DG2 driver code paths.
This disabled support is similar to what Intel engineers did when bringing up DG2/Alchemist Arc Graphics is leaving the PCI IDs commented out until ready to treat the OpenGL and Vulkan driver support as stable/supported.
The added but disabled Meteor Lake graphics IDs are 0x7d40, 0x7d45, 0x7d55, 0x7d60, and 0x7dd5. Ther Meteor Lake device information reaffirms that is already known for the integrated graphics is that they will be close to what is found with DG2/Alchemist discrete graphics hardware but in integrated form -- including features like Vulkan mesh shaders and ray-tracing to work with Meteor Lake integrated graphics.
So this patch is now part of Mesa 23.0 but don't expect the support to be enabled/advertised until a later release once ensuring the user-space API and all functionality is in good shape. Similarly, as of Linux 6.2 / DRM-Next the Meteor Lake support is still treated as experimental / behind the "force_probe" option.
Meteor Lake processors aren't expected to be released until late 2023 or even 2024 with there already being delay rumors. In which case there still are a few Linux kernel and Mesa releases to go where this new code can get squared away before enabling it and still having out-of-the-box support in time for launch day.
1 Comment