OSDN Git Service

Don't automatically destroy the buffer(s) passed to vaRenderPicture
authorXiang, Haihao <haihao.xiang@intel.com>
Wed, 4 Jan 2017 02:17:19 +0000 (10:17 +0800)
committerXiang, Haihao <haihao.xiang@intel.com>
Mon, 9 Jan 2017 05:30:29 +0000 (13:30 +0800)
commit3eb038aa13bdd785808286c0a4995bd7a1ef07e9
tree2a13b1d9aa1f6cf6351842aa0dbe2fad114e3b3d
parent53f4752fc3253076514e2c24fd3ec93ed771c62b
Don't automatically destroy the buffer(s) passed to vaRenderPicture

Instead the user must call vaDestroyBuffer() to destroy a buffer explicitly.

If following the previous API specification,
1. Violate "who allocate who release" principle
2. The user cannot re-use VA buffer flexibly
3. The user still has to call vaDestroyBuffer() to destroy the buffers which
   are not going to be passed to vaRenderPicture()

We discussed the change at https://bugs.freedesktop.org/show_bug.cgi?id=97970

v2: bump version to 0.40 because this is a incompatible change to VA-API

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
configure.ac
va/va.h
va/va_enc_h264.h
va/va_vpp.h