GNOME Bugzilla – Bug 795023
kmssink: add drm-fd property
Last modified: 2018-11-03 14:21:03 UTC
Created attachment 370572 [details] [review] patch for drm-fd property When I try to use two different pipelines (two different src, two different kmssink, and two different displays) but one single DRM device (in my case an i915) it fails because the device was in use by the first pipeline (single process). I added the ability to get/set the DRM device FD in kmssink. This solved my scenario. I think that passing or get the FD could be handy in other scenarios where you want to open the device earlier or you need to do something on the DRM device. I tested this patch on 1.14 branch and a simple application that start two pipelines in the same process for each output display. When the first pipeline is in the running state I get the DRM FD and set DRM FD on the second pipeline. Best Matteo Valdina
I was thinking about this yesterday, I and believe that using GstContext is better for this use case, because we could share a the drm-fd through the pipeline and through the application. The problem would be when using gst-launch.
I also think that same could be achieve with GstContext, it could later support multiple context type, like DRM cookies cookie, and would work automatically, if app take care of modes, from gst-launch-1.0. It's nice though, since it confirms it can work. For the performance issues, it would be very valuable to try patch from https://bugzilla.gnome.org/show_bug.cgi?id=793339
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/685.