Skip to content
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.

fix reset context bug && fix profile support bug #7

Merged
merged 2 commits into from
Apr 23, 2014

Conversation

zhongcong
Copy link
Contributor

No description provided.

@halleyzhao
Copy link
Contributor

-1

  1. cong, you are not using the latest code. in order to fix the profile issue on chromeos, i have updated the code.
  2. the original logical is to fail unsupported profile in VaapiDecoderBase::setupVA; is that too late for you? it is not a good idea to make hw assumption in decoder level.

@@ -64,6 +64,11 @@ static VAProfile getH264VAProfile(H264PPS * pps)
(pps->num_slice_groups_minus1 == 0 &&
!pps->redundant_pic_cnt_present_flag))
profile = VAProfileH264ConstrainedBaseline;
else {
ERROR("h264 baseline profile is not supported");
profile = VAProfileNone;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our decoder may running on different target. Do not assume it's no baseline profile supported.We need query this from VA.

@zhongcong
Copy link
Contributor Author

yes. profile should not be assumed here. i think that there are two way to refine:

  1. deliver profile to VaapiDecoderBase::setupVA, let intel-driver judge if it is supported.
  2. add a new function in ensureContext to have communication with intel-driver to judge the profile support.

if (parsedProfile != m_configBuffer.profile) {
DEBUG("H264: profile changed: old = %d, new = %d, \n",
m_configBuffer.profile, parsedProfile);
m_configBuffer.profile = parsedProfile;
m_configBuffer.flag |= HAS_VA_PROFILE;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here are exist code. why we not set the flag before your commit .

Zhong Cong added 2 commits April 22, 2014 15:09
Signed-off-by: Zhong Cong <congx.zhong@intel.com>
Signed-off-by: Zhong Cong <congx.zhong@intel.com>
@halleyzhao
Copy link
Contributor

+1
looks good to me

@xuguangxin
Copy link
Contributor

+1

@zhongcong
Copy link
Contributor Author

thanks. Now i can push my patch to 01org.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants