Simon Ser 85d7ad2eef backend/drm: allow legacy scan-out if FB props match ... Historically we haven't allowed direct scan-out for legacy KMS, because legacy misses the functionality to make sure a buffer can be scanned out. However with renderer v6 the backend can't figure out anymore whether the buffer comes from its internal swap-chain, because the backend doesn't have an internal swap-chain. The legacy KMS API guarantees that the driver won't reject a buffer as long as it's been allocated with the same parameters as the previous one. Let's check this in legacy_crtc_test.		2021-07-28 22:52:35 +02:00
..
atomic.c	backend/drm: remove backend arg from wlr_drm_interface.crtc_commit	2021-07-09 15:31:19 -04:00
backend.c	backend/drm: stop restoring CRTCs on exit	2021-07-20 15:33:26 +02:00
cvt.c	backend/drm: add support for custom modes	2019-10-27 10:46:47 -04:00
drm.c	backend/drm: implement get_primary_formats	2021-07-28 22:52:35 +02:00
legacy.c	backend/drm: allow legacy scan-out if FB props match	2021-07-28 22:52:35 +02:00
meson.build	backend: make DRM and libinput backends optional	2021-07-22 09:56:38 -04:00
properties.c	backend/drm: add support for the subconnector property	2021-01-17 12:42:25 +01:00
renderer.c	render/wlr_texture: put wlr_texture_from_buffer into the public API	2021-07-22 22:28:24 +02:00
util.c	backend/drm: add DRM_MODE_CONNECTOR_USB to conn_get_name	2021-07-21 08:47:35 +02:00