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 wrote:
> >>>
> The old vaAcquireBuffer
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 cases and provides
less inform
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 current vaExportSurfaceHandle(), but
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 already used by the O
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 have much use dir
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 co