Simon Ser f43ac6cf9c 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 (cherry picked from commit d2a5dbe104)		2024-08-23 09:30:33 -04:00
..
drm	backend/drm: use CRTCs in-order	2024-08-23 09:30:33 -04:00
headless	backend/headless: take wl_event_loop instead of wl_display	2024-01-25 15:05:36 +00:00
libinput	build: require libinput v1.19	2024-07-04 22:51:07 +02: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	backend/wayland: process initial events from globals correctly	2024-08-15 11:06:50 -04:00
x11	backend/x11: send correct keyboard layout	2024-05-26 12:52:42 +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