FS#65886 - [chromium] Please reconsider use_vaapi=true build

Attached to Project: Arch Linux
Opened by KJ Liew (liewkj) - Thursday, 19 March 2020, 02:30 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 20 June 2020, 12:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Please reconsider use_vaapi=true build


Additional info:
Chromium build with use_vaapi=true should be considered stable without any additional patch for its intended hardware based on Intel VAAPI and MESA VAAPI.
https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/vaapi.md#vaapi-on-linux
Additional upstream patch for Intel GPU on Wayland
https://chromium-review.googlesource.com/c/chromium/src/+/2013806
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 20 June 2020, 12:18 GMT
Reason for closing:  Implemented
Additional comments about closing:  chromium 83.0.4103.106-2
Comment by Jensen McKenzie (your_doomsday) - Monday, 13 April 2020, 14:09 GMT
In documentation you linked it says:

"This configuration is unsupported (see docs/linux/hw_video_decode.md), the following instructions are provided only as a reference for developers to test the code paths on a Linux machine."

Following above link it says:

** note NOTE THIS IS AN UNSUPPORTED CONFIGURATION AND LIKELY TO BE BROKEN AT ANY POINT IN TIME **

Why do you want to expose unsupported/broken configuration for all Arch Linux users?
Comment by KJ Liew (liewkj) - Thursday, 16 April 2020, 00:25 GMT
Unsupported != broken and/or unstable.

The fact that it is even documented to provide as reference for developers to test the code paths would tell that it is actually tested and working for most of the time. It is not enabled by default and typical users would have opted out without providing the required flags to enable video decode acceleration.

I only ask for the build to include "use_vaapi=true" and I *DO NOT* ask to make it enabled by default. Advanced users who wanted this would enable it with additional flags. Typical users would not be exposed to the feature. It is similar to many other accelerated features in Chromium that are not exposed unless explicitly turned on with additional flags (GPU rasterization, Zero-copy rasterizer, Out-of-process rasterization etc.)
Comment by Vignesh Balasubramaniam (viggy96) - Wednesday, 10 June 2020, 23:08 GMT
Please consider this change Arch, like the previous user said, the default would still be software encoding, but advanced users could still enable hardware acceleration with the additional flags.

Loading...