6 Commits

Author	SHA1	Message	Date
Sreerenj Balachandran	62d2d8ebf9	msdk: Add method to export dmabuf to VASurface ... Exporting DRM_PRIME fd to VASurface requires direct invocation of VA api VACreateSurface with VASurfaceAttribExternalBufferDescriptor and other necessary surface attributes. https://bugzilla.gnome.org/show_bug.cgi?id=794817	2018-05-30 16:22:49 -08:00
Hyunjun Ko	90491d889a	msdk: allocator: libva: check if it's already using dmabuf when mapping ... As long as we negotiate the "DMABuf" capsfeatures for now, map can't be working. So we need to confirm not to do it if using DMABuf memory. https://bugzilla.gnome.org/show_bug.cgi?id=793707	2018-04-02 15:49:32 -08:00
Hyunjun Ko	5df06545ef	msdk: adds new function to get dmabuf information from surface. ... https://bugzilla.gnome.org/show_bug.cgi?id=793707	2018-03-30 11:05:16 -08:00
Hyunjun Ko	bd8ffcb29d	msdk: allocator: get dmabuf handle during allocation if required ... https://bugzilla.gnome.org/show_bug.cgi?id=793707	2018-03-30 11:04:28 -08:00
Hyunjun Ko	762eb97092	msdk: specify the way to find a proper cached response by request ... The current way to find proper response by just comparing request's value is wrong. We need to compare the size of a frame and the number of suggested frames. Refer to the sample in https://github.com/Intel-Media-SDK/samples. https://bugzilla.gnome.org/show_bug.cgi?id=793707	2018-03-30 11:02:26 -08:00
Hyunjun Ko	4d860ec82b	msdk: adds frame allocator using libva ... Implements msdk frame allocator which is required from the driver. Also makes these functions global so that GstMsdkAllocator could use the allocated video memory later and couple with GstMsdkMemory. GstMsdkContext keeps allocation information such as mfxFrameAllocRequest and mfxFrameAllocResponse after allocation. https://bugzilla.gnome.org/show_bug.cgi?id=790752	2018-02-13 12:43:42 -09:00