>We can keep it like this for now, but I would prefer that we clean this up and
>change the radeon_vce so that it matches the begin/encode/end calls from
>VA-API.
>We should probably work on this together with the performance improvements.
>Regards,
>Christian.
Hi Christian,
Sure, I agree, we
Add necessary functions/changes for VAAPI encoding to buffer and picture. These
changes will allow driver to handle all Vaapi encode related operations. This
patch doesn't change the Vaapi decode behaviour.
Signed-off-by: Boyuan Zhang
---
src/gallium/state_trackers/va/buffer.c | 6 +
src
Am 20.07.2016 um 06:21 schrieb Zhang, Boyuan:
>> - context->decoder->begin_frame(context->decoder, context->target,
&context->desc.base);
>> + if (context->decoder->entrypoint != PIPE_VIDEO_ENTRYPOINT_ENCODE)
>> + context->decoder->begin_frame(context->decoder, context->target,
&context->de
>> - context->decoder->begin_frame(context->decoder, context->target,
>> &context->desc.base);
>> + if (context->decoder->entrypoint != PIPE_VIDEO_ENTRYPOINT_ENCODE)
>> + context->decoder->begin_frame(context->decoder, context->target,
>> &context->desc.base);
>Why do we do so here? Cou
Am 19.07.2016 um 00:43 schrieb Boyuan Zhang:
Add necessary functions/changes for VAAPI encoding to buffer and picture. These
changes will allow driver to handle all Vaapi encode related operations. This
patch doesn't change the Vaapi decode behaviour.
Signed-off-by: Boyuan Zhang
---
src/gal
Add necessary functions/changes for VAAPI encoding to buffer and picture. These
changes will allow driver to handle all Vaapi encode related operations. This
patch doesn't change the Vaapi decode behaviour.
Signed-off-by: Boyuan Zhang
---
src/gallium/state_trackers/va/buffer.c | 6 +
src
