From 2b498d1d134e2bcf3898c36bb087a540ffc30083 Mon Sep 17 00:00:00 2001
From: Arnav Singh <me@arnavion.dev>
Date: Thu, 20 Jun 2024 12:31:47 -0700
Subject: [PATCH] direct-mode: update Wayland section for the DRM leasing
 protocol

---
 direct-mode.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/direct-mode.md b/direct-mode.md
index d8e2cc4..7de298a 100644
--- a/direct-mode.md
+++ b/direct-mode.md
@@ -82,11 +82,9 @@ Lastly, when the VR software quits, the display is released with `VK_EXT_direct_
 
 # Wayland
 
-On vanilla wayland compositors HMD displays are not hidden, they appear in monitor configuration tools as conventional monitors.
+Some Wayland compositors recognize HMDs based on the same `non-desktop` kernel quirk mentioned above and make them available for direct access via the `drm-lease-v1` Wayland protocol. Monado's "wayland direct" target uses this protocol to acquire the HMD for direct mode.
 
-It is also not possible to acquire a display for direct mode.
-
-[Patches for a WIP mesa and a wayland protocol implementation can be found on Drew DeVault's blog](https://drewdevault.com/2019/08/09/DRM-leasing-and-VR-for-Wayland.html).
+If the compositor does not support the protocol or does not detect the HMD as a "non-desktop" output for any reason, the HMD will appear as a regular monitor. In this case, Monado should be run with its "wayland" target, forced via the `XRT_COMPOSITOR_FORCE_WAYLAND=1` environment variable if necessary. Alternatively, the compositor might provide some way to override its default detection and treat the HMD as a non-desktop output.
 
 # Vulkan on KMS/DRM
 
-- 
GitLab