[Mesa-dev] [PATCH] st/va: WIP remove nonesense HEVC picture id handling
Christian König
deathsimple at vodafone.de
Fri Dec 4 04:14:38 PST 2015
From: Christian König <christian.koenig at amd.com>
The picture id in this case is a VA-API surface handle, checking
for a certain value is can't be correct.
Does anybody have any idea what the original intention was and how
to fix it correctly?
Signed-off-by: Christian König <christian.koenig at amd.com>
---
src/gallium/state_trackers/va/picture_hevc.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/src/gallium/state_trackers/va/picture_hevc.c b/src/gallium/state_trackers/va/picture_hevc.c
index dc66b0f..28743ee 100644
--- a/src/gallium/state_trackers/va/picture_hevc.c
+++ b/src/gallium/state_trackers/va/picture_hevc.c
@@ -159,11 +159,6 @@ void vlVaHandlePictureParameterBufferHEVC(vlVaDriver *drv, vlVaContext *context,
for (i = 0 ; i < 15 ; i++) {
context->desc.h265.PicOrderCntVal[i] = hevc->ReferenceFrames[i].pic_order_cnt;
- unsigned int index = hevc->ReferenceFrames[i].picture_id & 0x7F;
-
- if (index == 0x7F)
- continue;
-
vlVaGetReferenceFrame(drv, hevc->ReferenceFrames[i].picture_id, &context->desc.h265.ref[i]);
if ((hevc->ReferenceFrames[i].flags & VA_PICTURE_HEVC_RPS_ST_CURR_BEFORE) && (iBefore < 8)) {
--
2.5.0
More information about the mesa-dev
mailing list