News: 0001304413

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Initial Bits Land In Mesa 22.0 For Intel Raptor Lake

([Intel] 3 Hours Ago Raptor Lake S)


In addition to [1]Mesa 22.0 landing Vulkan 1.3 support today with the Radeon RADV and Intel ANV Vulkan drivers, Mesa today also received initial support for next-gen Raptor Lake S processors.

With the in-development Linux 5.17 kernel there is [2]the initial i915 kernel driver support for Raptor Lake S so now that the DRM/KMS side has initial RPL-S support, Mesa has landed its dependent support.

This Raptor Lake S support in Mesa for their Iris Gallium3D (OpenGL) and ANV Vulkan drivers isn't all that big and is namely about adding a new platform and the new PCI IDs. There are six initial PCI IDs for Raptor Lake S including 0xa780, 0xa781, 0xa782, 0xa783, 0xa788, and 0xa789.

[3]Raptor Lake S continues to make use of Intel "Gen12" graphics seen since Tiger Lake and continue to be evolved upon, so the driver support path at this stage isn't really different from current Alder Lake graphics support besides the new identification.

The Raptor Lake S Mesa support is now [4]merged though expect it to continue to be refined and improved upon over the coming releases, just as the Intel i915 kernel driver support too will evolve ahead of the expected RPL-S debut around the end of 2022.



[1] https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Vulkan-1.3

[2] https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.17-DRM-Submitted

[3] https://www.phoronix.com/scan.php?page=news_item&px=Intel-Raptor-Lake-Graphics

[4] https://cgit.freedesktop.org/mesa/mesa/commit/?id=4e0eca7dc34942759638ab00eb006ba40284a7c5



phoronix Administrator Find all posts View Profile Close phoronix

"Pseudocode can be used to some extent to aid the maintenance
process. However, pseudocode that is highly detailed -
approaching the level of detail of the code itself - is not of
much use as maintenance documentation. Such detailed
documentation has to be maintained almost as much as the code,
thus doubling the maintenance burden. Furthermore, since such
voluminous pseudocode is too distracting to be kept in the
listing itself, it must be kept in a separate folder. The
result: Since pseudocode - unlike real code - doesn't have to be
maintained, no one will maintain it. It will soon become out of
date and everyone will ignore it. (Once, I did an informal
survey of 42 shops that used pseudocode. Of those 42, 0 [zero!],
found that it had any value as maintenance documentation."
--Meilir Page-Jones, "The Practical Guide to Structured
Design", Yourdon Press (c) 1988