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
..
atomic.c	backend/drm: add support for explicit sync APIs	2024-08-06 17:37:06 +00:00
backend.c	backend/drm: Free drm device name on error	2024-04-30 10:18:05 +02:00
drm.c	types/wlr_output: removing the useless pointer	2024-08-21 14:04:24 +00:00
fb.c	backend/drm: add drm_fb_copy()	2024-03-04 11:25:33 +01:00
gen_pnpids.sh	backend/drm: use libdisplay-info to parse EDID	2023-02-28 14:44:02 +00:00
legacy.c	backend/drm: Use cached vrr support flag	2024-06-21 14:18:34 +00:00
libliftoff.c	backend/drm: avoid "maybe uninitialized" warning	2024-06-05 01:07:24 +03:00
meson.build	add an option to enable/disable libliftoff	2024-06-05 22:33:05 -06:00
monitor.c	backend/drm: drop wl_display argument	2024-01-25 15:05:36 +00:00
properties.c	backend/drm: add support for explicit sync APIs	2024-08-06 17:37:06 +00:00
renderer.c	swapchain, damage_ring: Drop buffer age	2024-08-21 09:45:54 -04:00
util.c	backend/drm: use CRTCs in-order	2024-08-21 15:17:04 +00:00