https://bugs.freedesktop.org/show_bug.cgi?id=97075
Christian König <deathsimple at vodafone.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Priority|medium |high
--- Comment #1 from Christian König <deathsimple at vodafone.de> ---
Yeah, that is a known issue.
The current VA-API implementation waits for the result after sending a single
frame to the hardware.
The OpenMAX implementation pipelines the whole thing and waits for a result
after sending multiple frames to the hardware to chew on.
So with OpenMAX the hardware is always busy, while with VA-API it constantly
turns on/off.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160725/81f3cfea/attachment.html>
