commit | a01c25926534105d96c4b6712a7f176bf1d5ed7c | [log] [tgz] |
---|---|---|
author | Peter McNeeley <petermcneeley@chromium.org> | Fri Jun 11 22:20:20 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 11 22:20:20 2021 |
tree | 29d4210eb3b9e1b73937e20f8aae4eecfffe2317 | |
parent | d8acb061b0429624e67fbf235907ff8c3b93fd45 [diff] |
Basic delegated compositing prototype for LaCros This is the initial submission to support delegate compositing for LaCros. Here a custom overlay processor is used to forward texture and tile quads through Wayland over to Ash. Overall this mechanism has and will have significant parallels to CALayer on Apple. The quality level of the code and implementation in "overlay_processor_delegated.h/cc" is prototype and only activated by the "DelegatedCompositing" flag and only for LaCros. Flags required for this prototype to operate: (set in /etc/chrome_dev.conf) --lacros-chrome-additional-args= --enable-gpu-memory-buffer-compositor-resources #### --enable-features=DelegatedCompositing Design doc for prototype details: https://docs.google.com/document/d/ 1o6a-JTx42jKN21JuvIeEaWuqkmNVGdo33ogTseUkTpk/ edit?usp=sharing&resourcekey=0-hTc9nPF2GiFPEqZjzBPpYg Bug: 1203918 Change-Id: Ie455a51a13de1051b62f254a2c25051b702b4620 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2927343 Commit-Queue: Peter McNeeley <petermcneeley@google.com> Reviewed-by: Robert Kroeger <rjkroege@chromium.org> Reviewed-by: Kramer Ge <fangzhoug@chromium.org> Reviewed-by: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#891818}
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.