You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Simon Ser 0817c52a21 backend/drm: get rid of BO handle table ... The BO handle table exists to avoid double-closing a BO handle, which aren't reference-counted by the kernel. But if we can guarantee that there is only ever a single ref for each BO handle, then we don't need the BO handle table anymore. This is possible if we create the handle right before the ADDFB2 IOCTL, and close the handle right after. The handles are very short-lived and we don't need to track their lifetime. Because of multi-planar FBs, we need to be a bit careful: some FB planes might share the same handle. But with a small check, it's easy to avoid double-closing the same handle (which wouldn't be a big deal anyways). There's one gotcha though: drmModeSetCursor2 takes a BO handle as input. Saving the handles until drmModeSetCursor2 time would require us to track BO handle lifetimes, so we wouldn't be able to get rid of the BO handle table. As a workaround, use drmModeGetFB to turn the FB ID back to a BO handle, call drmModeSetCursor2 and then immediately close the BO handle. The overhead should be minimal since these IOCTLs are pretty cheap. Closes: https://github.com/swaywm/wlroots/issues/3164		3 years ago
..
atomic.c	backend/drm: introduce wlr_drm_connector_state	3 years ago
backend.c	backend/drm: get rid of BO handle table	3 years ago
cvt.c	backend/drm: add support for custom modes	5 years ago
drm.c	output: add presented flag to presentation event	3 years ago
legacy.c	backend/drm: get rid of BO handle table	3 years ago
meson.build	backend/drm: get rid of BO handle table	3 years ago
properties.c	backend/drm: add support for panel orientation	3 years ago
renderer.c	backend/drm: get rid of BO handle table	3 years ago
util.c	backend/drm: get rid of BO handle table	3 years ago