We can't connect cursor until drmOutput::initCursor
is called, which is done by drmBackend::updateOutputs.
Fix this by splitting the connect part into its own
drmBackend::connectCursor private function.
This allows to use the DRM legacy cursor API.
Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
[platforms/drm] Allow to specify to dumb buffers' format
Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
[platforms/drm] RFC/PoC: Support hardware cursors using DRM atomic API
This needs the new DRM AMEND uAPI in order to make sure
the cursor is committed on the same vblank as content.
Currently, the legacy cursor API is the best choice. Once the
AMEND uAPI is merged upstream, it'll be possible to switch to it.
Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>