Re: [FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-12 Thread Rostislav Pehlivanov
On 12 March 2018 at 22:46, Mark Thompson wrote: > On 12/03/18 17:40, Rostislav Pehlivanov wrote: > > On 12 March 2018 at 00:23, Mark Thompson wrote: > > > >> On 12/03/18 00:01, Rostislav Pehlivanov wrote: > >>> On 11 March 2018 at 22:41, Mark Thompson

Re: [FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-12 Thread Mark Thompson
On 12/03/18 17:40, Rostislav Pehlivanov wrote: > On 12 March 2018 at 00:23, Mark Thompson wrote: > >> On 12/03/18 00:01, Rostislav Pehlivanov wrote: >>> On 11 March 2018 at 22:41, Mark Thompson wrote: >>> The old vaAcquireBufferHandle() API works in fewer

Re: [FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-12 Thread Rostislav Pehlivanov
On 12 March 2018 at 00:23, Mark Thompson wrote: > On 12/03/18 00:01, Rostislav Pehlivanov wrote: > > On 11 March 2018 at 22:41, Mark Thompson wrote: > > > >> The old vaAcquireBufferHandle() API works in fewer cases and provides > >> less information than the

Re: [FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-11 Thread Mark Thompson
On 12/03/18 00:01, Rostislav Pehlivanov wrote: > On 11 March 2018 at 22:41, Mark Thompson wrote: > >> The old vaAcquireBufferHandle() API works in fewer cases and provides >> less information than the current vaExportSurfaceHandle(), but it exists >> on older versions and is

Re: [FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-11 Thread Rostislav Pehlivanov
On 11 March 2018 at 22:41, Mark Thompson wrote: > The old vaAcquireBufferHandle() API works in fewer cases and provides > less information than the current vaExportSurfaceHandle(), but it exists > on older versions and is already used by the OpenCL code. This probably > doesn't

[FFmpeg-devel] [PATCH 2/7] hwcontext_vaapi: Add support for legacy DRM mapping

2018-03-11 Thread Mark Thompson
The old vaAcquireBufferHandle() API works in fewer cases and provides less information than the current vaExportSurfaceHandle(), but it exists on older versions and is already used by the OpenCL code. This probably doesn't have much use directly, but it will be used to replace the ad-hoc OpenCL