Lines Matching refs:render

51 GFX devices (both display and render/GPU side) are really complex bits of
131 step and to grant clients GPU access without authenticating, render
132 nodes were introduced. Render nodes solely serve render clients, that
133 is, no modesetting or privileged ioctls can be issued on render nodes.
135 render nodes, it must advertise it via the DRIVER_RENDER DRM driver
136 capability. If not supported, the primary node must be used for render
139 If a driver advertises render node support, DRM core will create a
140 separate render node called renderD<num>. There will be one render node
146 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render
148 privileged ioctls on render nodes.
150 With render nodes, user-space can now control access to the render node
153 required. Instead, a client can open the render node and is immediately
155 via PRIME. FLINK from render node to legacy node is not supported. New
158 Besides dropping all modeset/global ioctls, render nodes also drop the
159 DRM-Master concept. There is no reason to associate render clients with
162 to run without a master object if they support render nodes. If, on the
165 cannot support render nodes.
174 Graphics devices (display and/or render) may be connected via USB (e.g.