diff --git a/docs/drivers/vc4.rst b/docs/drivers/vc4.rst index ae16eb21e9f..1a8ad887775 100644 --- a/docs/drivers/vc4.rst +++ b/docs/drivers/vc4.rst @@ -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 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 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 ` and use ``vc4_dump_hang_state my-app.hang``. Sometimes the hang file will diff --git a/docs/envvars.rst b/docs/envvars.rst index e58740dc0ef..2c1ace8e9c7 100644 --- a/docs/envvars.rst +++ b/docs/envvars.rst @@ -282,7 +282,7 @@ Intel driver environment variables emit messages binding tables ``capture-all`` 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`` emit messages about the clip unit (for old gens, includes the CLIP program)