OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: gpu -> GPU

Browse Source 
Reviewed-by: David Heidelberg <david.heidelberg@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19191>
This commit is contained in:
Erik Faye-Lund
2022-10-20 10:52:02 +02:00
committed by Marge Bot
parent a590043c77
commit 6dbb184ad7
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/drivers/vc4.rst
View File

@@ -76,7 +76,7 @@ the problem. Traces attached to bug reports should ideally be small.
For GPU hangs, if you can get a short apitrace that produces the For GPU hangs, if you can get a short apitrace that produces the
problem, that's still the best. If the problem takes a long time to problem, that's still the best. If the problem takes a long time to
reproduce or you can't capture it in a trace, describing how to reproduce or you can't capture it in a trace, describing how to
reproduce and including a gpu hang dump would be the most reproduce and including a GPU hang dump would be the most
useful. Install `vc4-gpu-tools useful. Install `vc4-gpu-tools
<https://github.com/anholt/vc4-gpu-tools/>` and use <https://github.com/anholt/vc4-gpu-tools/>` and use
``vc4_dump_hang_state my-app.hang``. Sometimes the hang file will ``vc4_dump_hang_state my-app.hang``. Sometimes the hang file will

2
docs/envvars.rst
View File

@@ -282,7 +282,7 @@ Intel driver environment variables
emit messages binding tables emit messages binding tables
``capture-all`` ``capture-all``
flag all buffers to be captured by the kernel driver when flag all buffers to be captured by the kernel driver when
generating an error stage after a gpu hang generating an error stage after a GPU hang
``clip`` ``clip``
emit messages about the clip unit (for old gens, includes the CLIP emit messages about the clip unit (for old gens, includes the CLIP
program) program)