Searched refs:DRM (Results 1 – 25 of 151) 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/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/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/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/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/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/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/weston/doc/sphinx/toc/ |
| D | test-suite.rst | 216 DRM-backend tests
219 DRM-backend tests require a DRM device, so they are a special case. To select a
222 to run DRM-backend tests is to set this environment variable with the card that
223 should run the tests. For instance, in order to run DRM-backend tests with
228 with master status in a DRM device. Also, this is the reason why we can not run
229 two or more DRM-backend tests simultaneously. Since the test suite tries to run
230 the tests in parallel, we have a lock mechanism to enforce that DRM-backend
234 Another specificity of DRM-backend tests is that they run using the non-default
|
| /third_party/weston/ |
| D | meson_options.txt | 9 description: 'Weston backend: DRM/KMS'
15 description: 'DRM/KMS backend support for VA-API screencasting'
99 description: 'Virtual remote output with GStreamer on DRM backend'
106 description: 'Virtual remote output with Pipewire on DRM backend'
|
| /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/libdrm/amdgpu/ |
| D | libdrm_amdgpu.pc.in | 7 Description: Userspace interface to kernel DRM services for amdgpu
|
| /third_party/libdrm/radeon/ |
| D | libdrm_radeon.pc.in | 7 Description: Userspace interface to kernel DRM services for radeon
|
| /third_party/libdrm/exynos/ |
| D | libdrm_exynos.pc.in | 7 Description: Userspace interface to exynos kernel DRM services
|
| /third_party/libdrm/omap/ |
| D | libdrm_omap.pc.in | 7 Description: Userspace interface to omap kernel DRM services
|
| /third_party/mesa3d/ohos/pkgconfig_template/ |
| D | libdrm.pc | 6 Description: Userspace interface to kernel DRM services
|
| /third_party/libdrm/freedreno/ |
| D | libdrm_freedreno.pc.in | 7 Description: Userspace interface to freedreno kernel DRM services
|
| /third_party/libdrm/nouveau/ |
| D | libdrm_nouveau.pc.in | 7 Description: Userspace interface to nouveau kernel DRM services
|
1234567