renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2025-01-02 18:54:10 +08:00
Code

drm/doc: Remove <term> from rendernode docs

Browse Source 
The stylesheet doesn't allow this in normal paragraphs.

Cc: David Herrmann <dh.herrmann@gmail.com>
Acked-by: David Herrmann <dh.herrmann@gmail.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This commit is contained in:
Daniel Vetter 2014-01-21 12:51:43 +01:00
parent 89d61fc0f5
commit 00153aebc2
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/DocBook/drm.tmpl
View File

@ -2673,8 +2673,8 @@ int (*resume) (struct drm_device *);</synopsis>
DRM core provides multiple character-devices for user-space to use. DRM core provides multiple character-devices for user-space to use.
Depending on which device is opened, user-space can perform a different Depending on which device is opened, user-space can perform a different
set of operations (mainly ioctls). The primary node is always created set of operations (mainly ioctls). The primary node is always created
and called <term>card&lt;num&gt;</term>. Additionally, a currently and called card&lt;num&gt;. Additionally, a currently
unused control node, called <term>controlD&lt;num&gt;</term> is also unused control node, called controlD&lt;num&gt; is also
created. The primary node provides all legacy operations and created. The primary node provides all legacy operations and
historically was the only interface used by userspace. With KMS, the historically was the only interface used by userspace. With KMS, the
control node was introduced. However, the planned KMS control interface control node was introduced. However, the planned KMS control interface
@ -2689,21 +2689,21 @@ int (*resume) (struct drm_device *);</synopsis>
nodes were introduced. Render nodes solely serve render clients, that nodes were introduced. Render nodes solely serve render clients, that
is, no modesetting or privileged ioctls can be issued on render nodes. is, no modesetting or privileged ioctls can be issued on render nodes.
Only non-global rendering commands are allowed. If a driver supports Only non-global rendering commands are allowed. If a driver supports
render nodes, it must advertise it via the <term>DRIVER_RENDER</term> render nodes, it must advertise it via the DRIVER_RENDER
DRM driver capability. If not supported, the primary node must be used DRM driver capability. If not supported, the primary node must be used
for render clients together with the legacy drmAuth authentication for render clients together with the legacy drmAuth authentication
procedure. procedure.
</para> </para>
<para> <para>
If a driver advertises render node support, DRM core will create a If a driver advertises render node support, DRM core will create a
separate render node called <term>renderD&lt;num&gt;</term>. There will separate render node called renderD&lt;num&gt;. There will
be one render node per device. No ioctls except PRIME-related ioctls be one render node per device. No ioctls except PRIME-related ioctls
will be allowed on this node. Especially <term>GEM_OPEN</term> will be will be allowed on this node. Especially GEM_OPEN will be
explicitly prohibited. Render nodes are designed to avoid the explicitly prohibited. Render nodes are designed to avoid the
buffer-leaks, which occur if clients guess the flink names or mmap buffer-leaks, which occur if clients guess the flink names or mmap
offsets on the legacy interface. Additionally to this basic interface, offsets on the legacy interface. Additionally to this basic interface,
drivers must mark their driver-dependent render-only ioctls as drivers must mark their driver-dependent render-only ioctls as
<term>DRM_RENDER_ALLOW</term> so render clients can use them. Driver DRM_RENDER_ALLOW so render clients can use them. Driver
authors must be careful not to allow any privileged ioctls on render authors must be careful not to allow any privileged ioctls on render
nodes. nodes.
</para> </para>