Lines Matching refs:render

60 GFX devices (both display and render/GPU side) are really complex bits of
140 step and to grant clients GPU access without authenticating, render
141 nodes were introduced. Render nodes solely serve render clients, that
142 is, no modesetting or privileged ioctls can be issued on render nodes.
144 render nodes, it must advertise it via the DRIVER_RENDER DRM driver
145 capability. If not supported, the primary node must be used for render
148 If a driver advertises render node support, DRM core will create a
149 separate render node called renderD<num>. There will be one render node
152 complete list of driver-independent ioctls that can be used on render
157 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render
159 privileged ioctls on render nodes.
161 With render nodes, user-space can now control access to the render node
164 required. Instead, a client can open the render node and is immediately
166 via PRIME. FLINK from render node to legacy node is not supported. New
169 Besides dropping all modeset/global ioctls, render nodes also drop the
170 DRM-Master concept. There is no reason to associate render clients with
173 to run without a master object if they support render nodes. If, on the
176 cannot support render nodes.
185 Graphics devices (display and/or render) may be connected via USB (e.g.