The documentation for render nodes indicates that only "PRIME-related" ioctls are valid on render nodes, but the documentation does not clarify what that means. If the reader is not familiar with PRIME, they may beleive this to be only the ioctls with "PRIME" in the name and not other ioctls such as set of syncobj ioctls. Clarify the situation for the reader by referencing where the reader will find a current list of valid ioctls.
Unified · Split
| @@ -148,7 +148,9 @@ clients together with the legacy drmAuth authentication procedure. · 147 unmodified lines | |||
| 148 | If a driver advertises render node support, DRM core will create a | 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 | 149 | separate render node called renderD<num>. There will be one render node |
| 150 | per device. No ioctls except PRIME-related ioctls will be allowed on | 150 | per device. No ioctls except PRIME-related ioctls will be allowed on |
| 151 | this node. Especially GEM_OPEN will be explicitly prohibited. Render | 151 | this node. Especially GEM_OPEN will be explicitly prohibited. For a |
| 152 | complete list of driver-independent ioctls that can be used on render | ||
| 153 | nodes, see the ioctls marked DRM_RENDER_ALLOW in drm_ioctl.c Render | ||
| 152 | nodes are designed to avoid the buffer-leaks, which occur if clients | 154 | nodes are designed to avoid the buffer-leaks, which occur if clients |
| 153 | guess the flink names or mmap offsets on the legacy interface. | 155 | guess the flink names or mmap offsets on the legacy interface. |
| 154 | Additionally to this basic interface, drivers must mark their | 156 | Additionally to this basic interface, drivers must mark their |