commit | 1ce9abc81fac01b1a1d91bddf57f37747fe5ced3 | [log] [tgz] |
---|---|---|
author | Jianhui Dai <jianhui.j.dai@intel.com> | Sat Jan 06 02:38:52 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jan 06 02:38:52 2024 |
tree | 97cd251b9d58e36f3f776d84268c5afc6d019f24 | |
parent | f3d30cbd284b435c73162099d7bedbb98e1d490e [diff] |
Allowing VA-API on Linux Ozone/Wayland VaapiWrapper has been updated to remove the usage of libva-x11 and the legacy VaapiVideoDecodeAccelerator, in favor of libva-drm only. This means now Linux Ozone/Wayland can share the same code path as Linux Ozone/X11. See CL:4938496. This CL removes the remaining libva-x11 codes from Ozone and VaapiWrapper, and allows VA-API by default on Linux Ozone/Wayland. Insofar as Linux + VA-API is not a supported platform (IOW it's a best effort) and this will allow developers and users to try and make it work on their machines. [1] [1] https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/gpu/vaapi.md#vaapi-on-linux Test On Linux X11: -enable-features=VaapiVideoDecodeLinuxGL \ --use-gl=angle --use-angle=gl \ --ozone-platform=x11 Test On Linux Wayland: -enable-features=VaapiVideoDecodeLinuxGL \ --use-gl=angle --use-angle=gl \ --ozone-platform=wayland Bug: 1326754,1116701 Change-Id: I6d6bf781833a7752d23dafb2b63112c2fc81b17a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3646633 Reviewed-by: Miguel Casas-Sanchez <mcasas@chromium.org> Reviewed-by: Nick Yamane <nickdiego@igalia.com> Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by: Peter McNeeley <petermcneeley@chromium.org> Commit-Queue: Jianhui J Dai <jianhui.j.dai@intel.com> Cr-Commit-Position: refs/heads/main@{#1243718}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.