From 1c848c89d53fcaf834e875fdb47779fd3cce071e Mon Sep 17 00:00:00 2001 From: carpalis Date: Mon, 23 Oct 2017 10:23:35 +0200 Subject: genX_mfd: remove mapping of I frame to BI frame This mapping does not make sense. Unless the mapping is some workaround for a hardware quirk, we should be able to safely remove it. If this breaks things, we can always put it back accompanied with an explanation in the code. Signed-off-by: Jerome Borsboom --- src/gen8_mfd.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'src/gen8_mfd.c') diff --git a/src/gen8_mfd.c b/src/gen8_mfd.c index 962cb153..5dcccb7c 100644 --- a/src/gen8_mfd.c +++ b/src/gen8_mfd.c @@ -1561,10 +1561,6 @@ gen8_mfd_vc1_pic_state(VADriverContextP ctx, else ptype = pic_param->picture_fields.bits.picture_type; - if (profile == GEN7_VC1_ADVANCED_PROFILE && - picture_type == GEN7_VC1_I_PICTURE) - picture_type = GEN7_VC1_BI_PICTURE; - if (picture_type == GEN7_VC1_I_PICTURE || picture_type == GEN7_VC1_BI_PICTURE) /* I picture */ trans_ac_y = pic_param->transform_fields.bits.transform_ac_codingset_idx2; else { -- cgit v1.2.1