Simon Ser d2a5dbe104 backend/drm: use CRTCs in-order ... When lighting up a new connector, we'd use the last CRTC instead of the first one. This causes issues because drivers have the expectation that userspace will match CRTCs to connectors in-order [1]. The order has regressed a long time ago in 5b13b8a12c ("backend/drm: consider continue not using resources"). That commit was a fix to avoid moving a connector between CRTCs [2]. Revert that commit and use a different approach: even if we've found a solution, always try not using a CRTC in the hope that we'll find another solution with less CRTC replacements. [1]: https://lore.kernel.org/dri-devel/20240612141903.17219-2-ville.syrjala@linux.intel.com/ [2]: https://github.com/swaywm/wlroots/issues/1230 Closes: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3098		2024-08-21 15:17:04 +00:00
..
drm	backend/drm: use CRTCs in-order	2024-08-21 15:17:04 +00:00
headless	backend/headless: take wl_event_loop instead of wl_display	2024-01-25 15:05:36 +00:00
libinput	seat/pointer: handle duplicate presses/releases correctly	2024-08-06 22:53:08 +00:00
multi	backend/multi: implement wlr_backend_impl.{test,commit}	2024-03-14 22:03:10 +00:00
session	backend/session: use "KMS" instead of "DRM" in log messages	2024-06-17 09:43:38 +02:00
wayland	types/wlr_output: removing the useless pointer	2024-08-21 14:04:24 +00:00
x11	types/wlr_output: removing the useless pointer	2024-08-21 14:04:24 +00:00
backend.c	backend: add wlr_backend_{test,commit}()	2024-03-14 22:03:10 +00:00
meson.build	backend/session: make optional	2022-11-25 16:15:29 +00:00