Simon Ser e804de923d backend/drm: clarify error message on drmModeAddFB fallback ... The previous code would always print "falling back to legacy method", even if the format wasn't ARGB8888. Drop get_fb_for_bo_legacy, since the code can just be inlined without hurting readability. Ideally we should only fallback to drmModeAddFB if the error code indicates the BE failure, but the original PR [1] doesn't say what error code is returned by the kernel. [1]: https://github.com/swaywm/wlroots/pull/2569		2021-04-26 23:12:53 +02:00
..
atomic.c	backend/drm: downgrade test-only commit failure log level	2021-04-06 20:35:15 +02:00
backend.c	Make implementation function lists static const	2021-02-05 10:04:20 +01:00
cvt.c	backend/drm: add support for custom modes	2019-10-27 10:46:47 -04:00
drm.c	backend/drm: terminate display on drmHandleEvent failure	2021-04-14 23:56:56 +02:00
legacy.c	backend/drm: stop using surface size for BO	2021-01-10 11:24:44 +01:00
meson.build	meson: Various improvements	2019-12-23 07:48:29 -05:00
properties.c	backend/drm: add support for the subconnector property	2021-01-17 12:42:25 +01:00
renderer.c	render: rename get_dmabuf_render_formats into get_render_formats	2021-04-15 17:10:06 +02:00
util.c	backend/drm: clarify error message on drmModeAddFB fallback	2021-04-26 23:12:53 +02:00