Simon Ser 0a9886cc45 renderonly: write down usage rules ... The renderonly helpers are extremely easy to mis-use. Write down the expectations. I've seen *many* mistakes in the past, including: - Forgetting to create the scanout resource on import [1] [2], causing bugs such as [3]. - Assuming the scanout resource always exists [4]. - Returning a GEM handle valid for the driver's internal DRM FD, but invalid for the caller's DRM FD [5]. - Not implementing resource_get_param, breaking stride/offset/modifier queries when no scanout resource is available [6] [7]. Signed-off-by: Simon Ser <contact@emersion.fr> Reviewed-by: Lucas Stach <l.stach@pengutronix.de> Reviewed-by: Daniel Stone <daniels@collabora.com> [1]: 4aac98f8a6 [2]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12018 [3]: https://github.com/swaywm/wlroots/issues/2795 [4]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12081 [5]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12074 [6]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12362 [7]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12370 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12418>		2021-12-20 12:42:03 +01:00
..
renderonly.c	renderonly: don't complain when GPU import fails	2021-08-09 23:41:04 +02:00
renderonly.h	renderonly: write down usage rules	2021-12-20 12:42:03 +01:00