Public bug reported: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: originate-from-2016915 ** Tags added: originate-from-2016915 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
