For such use case, the pipeline is: decode->encode->send to network.
The local decode/playback and the encode process are seperated, thus it
needs the buffer sharing b/w the decode and encode in seperate process.
This API creates/wraps the decoded surface into an encode surface. Its
input parameter is the kernel buffer handle of decoded surface which is
only understandable by driver implementation.

Change-Id: I7953ecf3b7333c1cdb6af5a0f45b054c8840f8e2
Signed-off-by: jiguoliang <guoliangx.ji@intel.com>
Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

POC should be integer.

Change-Id: I75281aafa148c88f0de58981969e1c43ea8d2684
Signed-off-by: ywan171 <yi.a.wang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

I didn't see this issue until I upgraded my system recently.
It's evident the default behavior of the linker is changed.
Explicitly adding the missing libraries to the link step can resolve
this issue.
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Make sure to use our internal functions. In particular, we override
some DRM functions and they have to be used. e.g. this fixes VA/GLX.

VA_DECODE_SLICE_MISSING --> VADecodeSliceMissing
VA_DECODE_MB_ERROR --> VADecodeMBError
Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Hi,

This patch fixes the following error.

X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  137 (DRI2)
  Minor opcode of failed request:  4 (DRI2DestroyDrawable)
  Resource id in failed request:  0x4800001
  Serial number of failed request:  30
  Current serial number in output stream:  32

The X drawable can die before we notice it in free_drawable_hashtable(),
called through vaTerminate(). This patch is ported from Mesa (GLX/DRI2).

Regards,
Gwenole.

Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

vatrace:print H263 decode paramters
test/putsurfac: create drawable with a geometry from commandline
va.h: add BGRA fourcc
Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

This fixes https://bugs.freedesktop.org/show_bug.cgi?id=38628Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Change-Id: Ib39b436865c2b665dc49c916d5f364f03e8c79b5
igned-off-by: Austin Yuan <shengquan.yuan@gmail.com>

This fixes broken putsurface on X11
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Previously a VA display will be shared if a native display is shared by multiple threads,
it will casue some thread safety issue in a multi-threaded program.

Remove the global VADisplayContextP pDisplayContexts which is not thread safe
Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Edgar Hucek <gimli@dark-green.com>
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Edgar Hucek <gimli@dark-green.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

We should use _XReplay. _XSend will introduce more CPU usage
Signed-off-by: Edgar Hucek <gimli@dark-green.com>
Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>