Documentation: dmaengine: Correct reference to glReadPixels()

[PATCH] Documentation: dmaengine: Correct reference to glReadPixels()

Nathan Lynch via B4 Relay posted 1 patch 1 year, 2 months ago

Download mbox

Documentation/driver-api/dmaengine/provider.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Expand all Fold all

[PATCH] Documentation: dmaengine: Correct reference to glReadPixels()

Posted by Nathan Lynch via B4 Relay 1 year, 2 months ago

From: Nathan Lynch <nathan.lynch@amd.com>

The author very likely meant "glReadPixels()" instead of
"glReadpielx()", which does not appear in the OpenGL API.

https://registry.khronos.org/OpenGL-Refpages/gl4/html/glReadPixels.xhtml

Signed-off-by: Nathan Lynch <nathan.lynch@amd.com>
---
 Documentation/driver-api/dmaengine/provider.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/driver-api/dmaengine/provider.rst b/Documentation/driver-api/dmaengine/provider.rst
index 3085f8b460fa5514bf95d07e9c7120c19f2d467b..48ad4fd6e2773ab4e4ca5bcb851c0204295ab56f 100644
--- a/Documentation/driver-api/dmaengine/provider.rst
+++ b/Documentation/driver-api/dmaengine/provider.rst
@@ -172,8 +172,8 @@ Currently, the types available are:
   - It's usually used for copying pixel data between host memory and
     memory-mapped GPU device memory, such as found on modern PCI video graphics
     cards. The most immediate example is the OpenGL API function
-    ``glReadPielx()``, which might require a verbatim copy of a huge framebuffer
-    from local device memory onto host memory.
+    ``glReadPixels()``, which might require a verbatim copy of a huge
+    framebuffer from local device memory onto host memory.
 
 - DMA_XOR
 

---
base-commit: 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b
change-id: 20241009-doc-dmaengine-glreadpixels-8b3452468ec2

Best regards,
-- 
Nathan Lynch <nathan.lynch@amd.com>