From: GitLab M. <git...@ke...> - 2022-04-19 20:16:01
|
man/drm-kms.7.rst | 4 ++-- man/drm.7.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) New commits: commit 62e25c8baac80d6af1287c964d5d83eb255ef339 Author: Matt Turner <mat...@gm...> Date: Tue Apr 19 13:10:57 2022 -0700 man: Add formatting to drmModeGetConnector reference Signed-off-by: Matt Turner <mat...@gm...> diff --git a/man/drm-kms.7.rst b/man/drm-kms.7.rst index 7a4151ae..587d7eb7 100644 --- a/man/drm-kms.7.rst +++ b/man/drm-kms.7.rst @@ -102,7 +102,7 @@ for the selected connector. See the *Examples* section below for more information. All valid modes for a connector can be retrieved with a call to -drmModeGetConnector3 You need to select the mode you want to use and save it. +**drmModeGetConnector**\ (3) You need to select the mode you want to use and save it. The first mode in the list is the default mode with the highest resolution possible and often a suitable choice. commit 37d50e1cbfdb48a70e360c2c412568d3ed33a8aa Author: Matt Turner <mat...@gm...> Date: Tue Apr 19 11:53:55 2022 -0700 man: Fix some typos Signed-off-by: Matt Turner <mat...@gm...> diff --git a/man/drm-kms.7.rst b/man/drm-kms.7.rst index e91fbe27..7a4151ae 100644 --- a/man/drm-kms.7.rst +++ b/man/drm-kms.7.rst @@ -108,7 +108,7 @@ possible and often a suitable choice. After you have a working connector+CRTC+mode combination, you need to create a framebuffer that is used for scanout. Memory buffer allocation is -driver-depedent and described in **drm-memory**\ (7). You need to create a +driver-dependent and described in **drm-memory**\ (7). You need to create a buffer big enough for your selected mode. Now you can create a framebuffer object that uses your memory-buffer as scanout buffer. You can do this with **drmModeAddFB**\ (3) and **drmModeAddFB2**\ (3). diff --git a/man/drm.7.rst b/man/drm.7.rst index c9b5696f..df2c1c74 100644 --- a/man/drm.7.rst +++ b/man/drm.7.rst @@ -73,7 +73,7 @@ driver dependent. However, two generic frameworks are available that are used by most DRM drivers. These are the *Translation Table Manager* (TTM) and the *Graphics Execution Manager* (GEM). They provide generic APIs to create, destroy and access buffers from user-space. However, -there are still many differences between the drivers so driver-depedent +there are still many differences between the drivers so driver-dependent code is still needed. Many helpers are provided in *libgbm* (Graphics Buffer Manager) from the *Mesa* project. For more information on DRM memory management, see **drm-memory**\ (7). |