Lines Matching refs:DRM

6 DRM Memory Management
35 Almost all in-kernel DRM hardware drivers support an API called *Dumb-Buffers*.
44 with the DRM API. You can create framebuffers with **drmModeAddFB**\ (3) and
47 requests the DRM subsystem to prepare the buffer for memory-mapping and returns
96 contain an offset that can be used with **mmap**\ (2) on the DRM
100 ``DRM_IOCTL_MODE_DESTROY_DUMB``. If you close the DRM file-descriptor, all open
124 *GEM* stands for *Graphics Execution Manager* and is a generic DRM
134 flow within the linux DRM subsystem. However, GEM is not a complete framework
141 All GEM APIs are defined as **ioctl**\ (2) on the DRM file descriptor. An
143 DRM-Master to access the GEM subsystem. A driver that does not support GEM will
181 that has access to the DRM device and is authenticated via
182 **drmAuthMagic**\ (3) to the current DRM-Master, can *guess* the name and open
221 DRM devices. This does *not* require any windowing-system like X11, but can
222 also be done on raw DRM devices. However, this is beyond the scope of this
246 This examples shows how to create a dumb-buffer via the generic DRM API.
288        /* DRM buffer preparation failed; see "errno" */