Searched refs:DRM (Results 1 – 25 of 162) sorted by relevance
1234567
| /third_party/ltp/testcases/kernel/device-drivers/drm/kernel_space/ |
| D | tdrm.c | 49 static drm_pci_list_t DRM(idlist)[] =
56 #define DRIVER_CARD_LIST DRM(idlist)
59 static struct file_operations DRM(fops) = { \
61 .open = DRM(open), \
62 .flush = DRM(flush), \
63 .release = DRM(release), \
64 .ioctl = DRM(ioctl), \
65 .mmap = DRM(mmap), \
66 .read = DRM(read), \
67 .fasync = DRM(fasync), \
[all …]
|
| D | README | 1 Note on the DRM testcases, the kernel modules will load but all the tests
|
| /third_party/libdrm/man/ |
| D | drm.7.rst | 21 The *Direct Rendering Manager* (DRM) is a framework to manage *Graphics
32 the DRM character device. The *libdrm* library provides wrappers for these
35 When a GPU is detected, the DRM system loads a driver for the detected
46 All DRM devices provide authentication mechanisms. Only a DRM master is
48 can be DRM master at a time. See **drmSetMaster**\ (3) for information
49 on how to become DRM master and what the limitations are. Other DRM users
50 can be authenticated to the DRM-Master via **drmAuthMagic**\ (3) so they
57 is called *Mode-Setting*. This is restricted to the current DRM master.
58 Historically, this was implemented in user-space, but new DRM drivers
61 API provided by DRM. This includes allocating framebuffers, selecting
[all …]
|
| D | drmHandleEvent.3.rst | 6 read and process pending DRM events
23 ``drmHandleEvent`` processes outstanding DRM events on the DRM
25 the DRM file-descriptor has polled readable; it will read the events and
|
| D | drmAvailable.3.rst | 6 determine whether a DRM kernel driver has been loaded
23 ``drmAvailable`` allows the caller to determine whether a kernel DRM
29 ``drmAvailable`` returns 1 if a DRM driver is currently loaded.
|
| D | drm-memory.7.rst | 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
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/chapters/VK_EXT_acquire_drm_display/ |
| D | acquire_drm_display.txt | 5 [open,refpage='vkAcquireDrmDisplayEXT',desc='Acquire access to a VkDisplayKHR using DRM',type='prot…
8 Rendering Manager (DRM) interface, call:
13 * pname:drmFd DRM primary file descriptor.
22 The DRM FD must have DRM master permissions.
26 The provided DRM fd should not be closed before the display is released,
32 [open,refpage='vkGetDrmDisplayEXT',desc='Query the VkDisplayKHR corresponding to a DRM connector ID…
34 Before acquiring a display from the DRM interface, the caller may want to
42 * pname:drmFd DRM primary file descriptor.
43 * pname:connectorId Identifier of the specified DRM connector.
|
| /third_party/skia/third_party/externals/egl-registry/extensions/EXT/ |
| D | EGL_EXT_device_drm.txt | 45 EGL_EXT_device_drm requires a DRM driver.
49 EGL_EXT_output_drm requires a DRM driver which supports KMS.
69 EGL and DRM/KMS. An EGL implementation which provides these
70 extensions must have access to sufficient knowledge of the DRM
75 a generic fashion by layering on top of DRM, or EGL and DRM backends
117 EGLDeviceEXTs may be mapped to DRM device files.
119 To obtain a DRM device file for an EGLDeviceEXT, call
129 descriptor with DRM master permissions on the DRM device associated
131 If the file descriptor does not refer to the correct DRM device or
137 If EGL requires the use of the DRM file descriptor beyond the duration
[all …]
|
| /third_party/EGL/extensions/EXT/ |
| D | EGL_EXT_device_drm.txt | 45 EGL_EXT_device_drm requires a DRM driver.
49 EGL_EXT_output_drm requires a DRM driver which supports KMS.
69 EGL and DRM/KMS. An EGL implementation which provides these
70 extensions must have access to sufficient knowledge of the DRM
75 a generic fashion by layering on top of DRM, or EGL and DRM backends
117 EGLDeviceEXTs may be mapped to DRM device files.
119 To obtain a DRM device file for an EGLDeviceEXT, call
129 descriptor with DRM master permissions on the DRM device associated
131 If the file descriptor does not refer to the correct DRM device or
137 If EGL requires the use of the DRM file descriptor beyond the duration
[all …]
|
| D | EGL_EXT_device_drm_render_node.txt | 46 to query the DRM device node file associated with a given
72 "To obtain a DRM device file for the render node associated with an
76 "/dev/dri/renderDN"), or NULL if the device has no associated DRM
84 if the device has no associated DRM primary node. If
|
| /third_party/mesa3d/docs/_extra/specs/ |
| D | MESA_drm_image.spec | 35 Linux DRM mode setting and memory management drivers. The extension
37 lets the application get the DRM buffer handles.
82 To create a DRM EGLImage, call
96 should be usable as a scanout buffer with the DRM kernel
99 underlying DRM buffer name. EGL_DRM_BUFFER_USE_CURSOR_MESA
104 To create a process local handle or a global DRM name for a
114 written to <name>, the handle (local to the DRM file descriptor,
115 for use with DRM kernel modesetting API) is written to <handle> if
132 an existing DRM buffer name, it doesn't seem right to overload
136 querying the DRM EGLImage attributes (name, handle, and stride)?
|
| /third_party/EGL/extensions/MESA/ |
| D | EGL_MESA_drm_image.txt | 35 Linux DRM mode setting and memory management drivers. The extension
37 lets the application get the DRM buffer handles.
82 To create a DRM EGLImage, call
96 should be usable as a scanout buffer with the DRM kernel
99 underlying DRM buffer name. EGL_DRM_BUFFER_USE_CURSOR_MESA
104 To create a process local handle or a global DRM name for a
114 written to <name>, the handle (local to the DRM file descriptor,
115 for use with DRM kernel modesetting API) is written to <handle> if
132 an existing DRM buffer name, it doesn't seem right to overload
136 querying the DRM EGLImage attributes (name, handle, and stride)?
[all …]
|
| /third_party/skia/third_party/externals/egl-registry/extensions/MESA/ |
| D | EGL_MESA_drm_image.txt | 35 Linux DRM mode setting and memory management drivers. The extension
37 lets the application get the DRM buffer handles.
82 To create a DRM EGLImage, call
96 should be usable as a scanout buffer with the DRM kernel
99 underlying DRM buffer name. EGL_DRM_BUFFER_USE_CURSOR_MESA
104 To create a process local handle or a global DRM name for a
114 written to <name>, the handle (local to the DRM file descriptor,
115 for use with DRM kernel modesetting API) is written to <handle> if
132 an existing DRM buffer name, it doesn't seem right to overload
136 querying the DRM EGLImage attributes (name, handle, and stride)?
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
| D | VK_EXT_physical_device_drm.txt | 18 This extension provides new facilities to query DRM properties for physical
19 devices, enabling users to match Vulkan physical devices with DRM nodes on
27 DRM defines multiple device node types.
35 To query DRM properties for a physical device, chain
|
| D | VK_EXT_image_drm_format_modifier.txt | 37 === Introduction to DRM Format Modifiers
94 _Modifier_-capable APIs often pair _modifiers_ with DRM formats, which are
98 DRM formats.
99 The application must convert between elink:VkFormat and DRM format when it
100 sends or receives a DRM format to or from an external API.
102 The mapping from elink:VkFormat to DRM format is lossy.
103 Therefore, when receiving a DRM format from an external API, often the
105 DRM format to a elink:VkFormat.
106 For example, DRM formats do not distinguish between RGB and sRGB (as of
110 The mapping between elink:VkFormat and DRM format is also incomplete.
[all …]
|
| /third_party/mesa3d/src/drm-shim/ |
| D | README.md | 1 # DRM shim - Fake GEM kernel drivers in userspace for CI
11 - Doesn't know how to handle DRM fds getting passed over the wire from
21 Since this will effectively fake another DRM device to your system,
23 to use it if it's not the only DRM device present. Setting
|
| /third_party/libdrm/freedreno/kgsl/ |
| D | README | 12 DRM interface for GEM, which is basically sufficient to have DRI2
15 quite how I'd write a DRM driver, but at this stage it is useful for
25 module or a DRM driver.. it is just an attempt to paper over a non-
|
| /third_party/libdrm/ |
| D | README.rst | 4 This is libdrm, a userspace library for accessing the DRM, direct rendering
10 New functionality in the kernel DRM drivers typically requires a new libdrm,
|
| D | libdrm.pc.in | 7 Description: Userspace interface to kernel DRM services
|
| /third_party/libdrm/vc4/ |
| D | libdrm_vc4.pc.in | 7 Description: Userspace interface to vc4 kernel DRM services
|
| /third_party/libdrm/intel/ |
| D | libdrm_intel.pc.in | 7 Description: Userspace interface to intel kernel DRM services
|
| /third_party/libdrm/etnaviv/ |
| D | libdrm_etnaviv.pc.in | 7 Description: Userspace interface to etnaviv kernel DRM services
|
| /third_party/libdrm/tegra/ |
| D | libdrm_tegra.pc.in | 7 Description: Userspace interface to Tegra kernel DRM services
|
| /third_party/mesa3d/docs/drivers/ |
| D | v3d.rst | 11 <https://www.kernel.org/doc/html/latest/gpu/v3d.html>`__ kernel DRM
13 4, the kernel uses the vc4 DRM driver for display support, so Mesa
|
| /third_party/libdrm/radeon/ |
| D | libdrm_radeon.pc.in | 7 Description: Userspace interface to kernel DRM services for radeon
|
1234567