https://bugs.freedesktop.org/show_bug.cgi?id=110140
--- Comment #7 from Rafał Miłecki zajec5@gmail.com --- Thanks for looking at this Leo!
Initially I didn't realize the consequences of your patch. I hopefully understand it now.
Before the commit 36258308a794 ("st/va: fix the incorrect max profiles report") my Chromium was simply NOT USING any Video Acceleration. Chromium was complaining with the following errors: [21202:21202:0317/122002.223002:ERROR:vaapi_wrapper.cc(587)] : vaQueryConfigProfiles returned: 14 [21202:21202:0317/122002.223045:ERROR:vaapi_wrapper.cc(587)] : vaQueryConfigProfiles returned: 14
So your change didn't introduce any regression in JPEG hardware decoding. It only exposed an existing bug by allowing Chromium to use Video Acceleration.
*****
Let me provide some new (hopefully useful) info on this problem:
1) This problem is clearly about the JPEG decoding. If I revert commit 55e7de7b1935 ("radeonsi: enable vcn jpeg decode for raven") from any recent branch (18.3, 19.0 or master) the problem disappears.
2) The problem exists from the beginning. If I do: git checkout 55e7de7b1935 git cherry-pick 36258308a794 git cherry-pick dafa02c980c1 I get a Chromium with working Video Acceleration AND half bottom of webcam frames being green.
3) I tested few branches: 18.3: bottom half of webcam frames are green 19.0: whole webcam frames are green master: whole webcam frames are green
As you can see things got worse with the 19.0 branch (frames are totally green instead of half green). That regression was added by the commit 1b25d340b791 ("radeonsi: use compute for resource_copy_region when possible"). Hopefully this is some hint on what's wrong and what's causing the original problem.
*****
Leo: I didn't try any other players, I've yet to learn how to use JPEG hw decoding with some other application/player.