> Yes, exactly. And Wayland ignored it for years, from the start, and only later slowly adopted it as an extension.
DRM is not part of Wayland, and Wayland does not use DRM. Wayland is the protocol between the display server and application, DRM is a functionality provided by the kernel to allow user space applications to use and share graphics hardware.
The display server can use DRM, as will applications wanting to use OpenGL/Vulkan, but these are not "wayland".
Did you even read the use case for this? or just Googled 'Wayland DRM' and post the first link?
When VR headsets are exposed to user space, they appear as displays and subsequently the display server will control them (which isn't useful), this is just a protocol that allows clients (like games, SteamVR) to have control transferred so they can drive the VR headset instead. This is because multiple applications are not allowed to control the same display on the Linux kernel at the same time.
It does not make DRM/DRI part of Wayland. Again, it goes back to my original comment of "you use Wayland to communicate with the display server"
IIRC GNOME originally wanted to do this over Dbus, but there was opposition.
DRM is not part of Wayland, and Wayland does not use DRM. Wayland is the protocol between the display server and application, DRM is a functionality provided by the kernel to allow user space applications to use and share graphics hardware.
The display server can use DRM, as will applications wanting to use OpenGL/Vulkan, but these are not "wayland".