parent
2b997bb4bb
commit
37d50e1cbf
|
@ -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).
|
||||
|
|
|
@ -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).
|
||||
|
|
Loading…
Reference in New Issue