add output value interface for the values from driver#213
add output value interface for the values from driver#213XinfengZhang wants to merge 1 commit intointel:masterfrom
Conversation
XinfengZhang
force-pushed
the
crc
branch
2 times, most recently
from
9f1a193 to
b8415bc
Compare
sometimes , there are only one single value output a new buffer type is complex than a new interface Signed-off-by: XinfengZhang <carl.zhang@intel.com>
|
It might be sensible to have some sort of size information here. While the CRC hash in H.265 has a fixed size (number of planes * 16 bits, so usually 6 bytes), this API might be useful to use for something which doesn't. That could either be passed in the function (e.g. an extra argument |
| VAStatus | ||
| (*vaQueryOutputValue)( | ||
| VADriverContextP ctx, | ||
| VAContextID context, /* in */ |
There was a problem hiding this comment.
could also add the surfaceID 'VASurfaceID render_target' in this interface? it maybe more flexiable for usage.
| */ | ||
| VAStatus vaQueryOutputValue( | ||
| VADisplay dpy, | ||
| VAContextID context, |
There was a problem hiding this comment.
could also add the surfaceID 'VASurfaceID render_target' in this interface? it maybe more flexiable for usage.
There was a problem hiding this comment.
@Jexu, if add VASurfaceID render_target, it seems that it was changed to another function, calculate the input surface CRC?
3 participants
sometimes , there are only one single value output
a new buffer type is complex than a api call
Signed-off-by: XinfengZhang carl.zhang@intel.com