Skip to content

Don't bound surfaces to decoder context

This merge request supersedes !100 (closed) since I want a clean slate to think and work this issue.

While coding the experimental vah264dec I realized that Mesa and Intel drivers has no issues with surfaces not bounded to decoder's context, as @He_Junyan said and as ChromeOS currently works.

Since Mesa and Intel drivers are the only one in our allowed driver list, it wouldn't make sense put a quirk for this change. Thus, the decoder error NO_SURFACE doesn't make sense anymore.

These patches removes the whole NO_SURFACE handling and the hack to limit the output frame in reverse playback.

Merge request reports