chromium/src
0
Fork 0
Code Activity

docs/gpu/vaapi.md: fill in info about MESA_GLSL_CACHE_DISABLE

Browse Source 
In fact it is not necessary to set this env var but it is worth
mentioning to show that VA-API also works when the gpu process
is running in sandbox mode.

Bug: 917091
Change-Id: I0d7b43dcff4d7887e945b5d54d8d13d5244d1544
Reviewed-on: https://chromium-review.googlesource.com/c/1433032
Commit-Queue: Julien Isorce <julien.isorce@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625717}
This commit is contained in:
Julien Isorce
2019-01-24 18:05:59 +00:00
committed by Commit Bot
parent df506a4304
commit 0a0dd3a095
1 changed files with 9 additions and 5 deletions

14
docs/gpu/vaapi.md

@ -208,14 +208,18 @@ To run Chromium using VaAPI two arguments are necessary:
* `--ignore-gpu-blacklist`
* `--use-gl=desktop` or `--use-gl=egl`
Also, the environment variable `MESA_GLSL_CACHE_DISABLE=false` should be set:
**TODO(crbug.com/917091): Further clarify the env variable and the flags**
```shell
MESA_GLSL_CACHE_DISABLE=false ./out/gn/chrome --ignore-gpu-blacklist --use-gl=egl
./out/gn/chrome --ignore-gpu-blacklist --use-gl=egl
```
Note that you can set the environment variable `MESA_GLSL_CACHE_DISABLE=false`
if you want the gpu process to run in sandboxed mode, see
[crbug.com/264818](https://crbug.com/264818). To check if the running gpu
process is sandboxed or not, just open `chrome://gpu` and search for
`Sandboxed` in the driver information table. In addition, passing
`--gpu-sandbox-failures-fatal=yes` will prevent the gpu process to run in
non-sandboxed mode.
Refer to the [previous section](#verify-vaapi) to verify support and use of
the VaAPI.