Am 24.06.2016 um 14:46 schrieb Ilia Mirkin:
On Fri, Jun 24, 2016 at 8:39 AM, Christian König
wrote:
Ilia and/or maybe other nouveau developers: You guys don't have any plans to
expose the NVidia encoding functionality through the OpenMAX/VA-API state
trackers in the near future don't you?
Not
On Fri, Jun 24, 2016 at 8:39 AM, Christian König
wrote:
> Ilia and/or maybe other nouveau developers: You guys don't have any plans to
> expose the NVidia encoding functionality through the OpenMAX/VA-API state
> trackers in the near future don't you?
Not in the near future, no. As far as I'm awa
On 06/24/2016 02:39 PM, Christian König wrote:
+if (pic->enable_low_level_control == true) {
Well using this enable_low_level_control switch to choose between two
sets of hardcoded values is clearly a no go.
For the motion estimation and most of the other flags I would say just
try to ex
+ if (pic->enable_low_level_control == true) {
Well using this enable_low_level_control switch to choose between two
sets of hardcoded values is clearly a no go.
For the motion estimation and most of the other flags I would say just
try to expose the parameters we have in the hardware
Signed-off-by: Boyuan Zhang
---
src/gallium/drivers/radeon/radeon_vce_52.c | 107 +
1 file changed, 79 insertions(+), 28 deletions(-)
diff --git a/src/gallium/drivers/radeon/radeon_vce_52.c
b/src/gallium/drivers/radeon/radeon_vce_52.c
index 56b6dd8..ac577e3 100644
--
