<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/uapi/drm/drm.h, branch v3.14.5</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/uapi/drm/drm.h?h=v3.14.5</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/uapi/drm/drm.h?h=v3.14.5'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-02-18T18:41:01Z</updated>
<entry>
<title>drm: add DRM_CAPs for cursor size</title>
<updated>2014-02-18T18:41:01Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexander.deucher@amd.com</email>
</author>
<published>2014-02-12T17:48:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8716ed4e7bed4e4c7e3f37940e950ddc0362f450'/>
<id>urn:sha1:8716ed4e7bed4e4c7e3f37940e950ddc0362f450</id>
<content type='text'>
Some hardware may not support standard 64x64 cursors.  Add
a drm cap to query the cursor size from the kernel.  Some examples
include radeon CIK parts (128x128 cursors) and armada (32x64 or 64x32).
This allows things like device specific ddxes to remove asics specific
logic and also allows xf86-video-modesetting to work properly with hw
cursors on this hardware. Default to 64 if the driver doesn't specify
a size.

Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Reviewed-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/bufs: remove handling of _DRM_GEM mappings</title>
<updated>2013-12-18T01:08:42Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2013-12-11T10:34:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=05f51722a154e73019434bd020e50ddb941046c5'/>
<id>urn:sha1:05f51722a154e73019434bd020e50ddb941046c5</id>
<content type='text'>
Gone with the new gem vma offset manager from David.

We can also ditch the uapi header definition from the enum since
userspace never used this. It ended up in there purely for historical
reasons (for reusing the old drm mmap code essentially), not because
userspace ever needed it.

Cc: David Herrmann &lt;dh.herrmann@gmail.com&gt;
Reviewed-by: David Herrmann &lt;dh.herrmann@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Add a STEREO_3D capability to the SET_CLIENT_CAP ioctl</title>
<updated>2013-10-01T05:45:27Z</updated>
<author>
<name>Damien Lespiau</name>
<email>damien.lespiau@intel.com</email>
</author>
<published>2013-09-25T15:45:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=61d8e3282541139cf5bb31e4c42f952a6cc168f8'/>
<id>urn:sha1:61d8e3282541139cf5bb31e4c42f952a6cc168f8</id>
<content type='text'>
This capability allows user space to control the delivery of modes with
the 3D flags set. This is to not play games with current user space
users not knowing anything about stereo 3D flags and that could try
to set a mode with one or several of those bits set.

So, the plan is to remove the stereo modes from the list of modes we
give to DRM clients by default, and let them through if we are being
told otherwise.

stereo_allowed is bound to the drm_file structure to make it a
per-client setting, not a global one.

v2: Replace clearing 3D flags by discarding the stereo modes now that
    they are regular modes.
v3: SET_CAP -&gt; SET_CLIENT_CAP rename (Chris Wilson)

Reviewed-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Signed-off-by: Damien Lespiau &lt;damien.lespiau@intel.com&gt;
Acked-by: Dave Airlie &lt;airlied@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm: Add a SET_CLIENT_CAP ioctl</title>
<updated>2013-10-01T05:45:26Z</updated>
<author>
<name>Damien Lespiau</name>
<email>damien.lespiau@intel.com</email>
</author>
<published>2013-09-25T15:45:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1c0814fed3a558146402713028cb7114734ec172'/>
<id>urn:sha1:1c0814fed3a558146402713028cb7114734ec172</id>
<content type='text'>
This ioctl can be used to turn some knobs in a DRM driver. The client
can ask the DRM core for an alternate view of the reality: it can be
useful to be able to instruct the core that the DRM client can handle
new functionnality that would otherwise break current ABI.

v2: Rename to ioctl from SET_CAP to SET_CLIENT_CAP (Chris Wilson)

Reviewed-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Signed-off-by: Damien Lespiau &lt;damien.lespiau@intel.com&gt;
Acked-by: Dave Airlie &lt;airlied@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm: Move the GET_CAP macros next to the corresponding ioctl structure</title>
<updated>2013-10-01T05:45:25Z</updated>
<author>
<name>Damien Lespiau</name>
<email>damien.lespiau@intel.com</email>
</author>
<published>2013-09-25T15:45:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a99b57dbc09bfff57acd8a7c20f25dfa6cb892a5'/>
<id>urn:sha1:a99b57dbc09bfff57acd8a7c20f25dfa6cb892a5</id>
<content type='text'>
It's a tiny bit more logical to find the different capabilities you can
use with the GET_CAP ioctl next to the structure rather than putting
them at the end of the file.

v2: Tab align the litterals (David Herrmann)
v3: Make it clearer that DRM_PRIME_CAP_EXPORT/IMPORT are flags of
    DRM_CAP_PRIME.
v4: Rebase on top of latest bits (DRM_CAP_ASYNC_PAGE_FLIP was
    introduced)

Reviewed-by: David Herrmann &lt;dh.herrmann@gmail.com&gt; (for v2)
Signed-off-by: Damien Lespiau &lt;damien.lespiau@intel.com&gt;
Acked-by: Dave Airlie &lt;airlied@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm: Advertise async page flip ability through GETCAP ioctl</title>
<updated>2013-08-29T23:25:13Z</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2013-07-23T01:50:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=62f2104f3fc11c4cfd1307429cb955bfa48dcb37'/>
<id>urn:sha1:62f2104f3fc11c4cfd1307429cb955bfa48dcb37</id>
<content type='text'>
Let applications know whether the kernel supports asynchronous page
flipping.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/gem: convert to new unified vma manager</title>
<updated>2013-07-25T10:47:06Z</updated>
<author>
<name>David Herrmann</name>
<email>dh.herrmann@gmail.com</email>
</author>
<published>2013-07-24T19:07:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0de23977cfeb5b357ec884ba15417ae118ff9e9b'/>
<id>urn:sha1:0de23977cfeb5b357ec884ba15417ae118ff9e9b</id>
<content type='text'>
Use the new vma manager instead of the old hashtable. Also convert all
drivers to use the new convenience helpers. This drops all the
(map_list.hash.key &lt;&lt; PAGE_SHIFT) non-sense.

Locking and access-management is exactly the same as before with an
additional lock inside of the vma-manager, which strictly wouldn't be
needed for gem.

v2:
 - rebase on drm-next
 - init nodes via drm_vma_node_reset() in drm_gem.c
v3:
 - fix tegra
v4:
 - remove duplicate if (drm_vma_node_has_offset()) checks
 - inline now trivial drm_vma_node_offset_addr() calls
v5:
 - skip node-reset on gem-init due to kzalloc()
 - do not allow mapping gem-objects with offsets (backwards compat)
 - remove unneccessary casts

Cc: Inki Dae &lt;inki.dae@samsung.com&gt;
Cc: Rob Clark &lt;robdclark@gmail.com&gt;
Cc: Dave Airlie &lt;airlied@redhat.com&gt;
Cc: Thierry Reding &lt;thierry.reding@gmail.com&gt;
Signed-off-by: David Herrmann &lt;dh.herrmann@gmail.com&gt;
Acked-by: Patrik Jakobsson &lt;patrik.r.jakobsson@gmail.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm: add hotspot support for cursors.</title>
<updated>2013-06-27T23:13:39Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2013-06-20T01:48:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4c813d4d759c0e6b83bfd73795e9526493556dc2'/>
<id>urn:sha1:4c813d4d759c0e6b83bfd73795e9526493556dc2</id>
<content type='text'>
So it looks like for virtual hw cursors on QXL we need to inform
the "hw" device what the cursor hotspot parameters are. This
makes sense if you think the host has to draw the cursor and interpret
clicks from it. However the current modesetting interface doesn't support
passing the hotspot information from userspace.

This implements a new cursor ioctl, that takes the hotspot info as well,
userspace can try calling the new interface and if it gets -ENOSYS it means
its on an older kernel and can just fallback.

Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Kill user_modes list and the associated ioctls</title>
<updated>2013-04-30T00:03:07Z</updated>
<author>
<name>Ville Syrjälä</name>
<email>ville.syrjala@linux.intel.com</email>
</author>
<published>2013-04-26T14:40:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c55b6b3da25aa3af36ec51a13a4ed15fef0d7a73'/>
<id>urn:sha1:c55b6b3da25aa3af36ec51a13a4ed15fef0d7a73</id>
<content type='text'>
There is no way to use modes added to the user_modes list. We never
look at the contents of said list in the kernel, and the only operations
userspace can do are attach and detach. So the only "benefit" of this
interface is wasting kernel memory.

Fortunately it seems no real user space application ever used these
ioctls. So just kill them.

Also remove the prototypes for the non-existing drm_mode_addmode_ioctl()
and drm_mode_rmmode_ioctl() functions.

v2: Use drm_noop instead of completely removing the ioctls

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm.h: Fix DRM compilation with bare-metal toolchain.</title>
<updated>2013-04-16T03:15:26Z</updated>
<author>
<name>Paul Sokolovsky</name>
<email>paul.sokolovsky@linaro.org</email>
</author>
<published>2013-04-12T23:28:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b6330548383cf18d608faf1c2dc0c81c60476233'/>
<id>urn:sha1:b6330548383cf18d608faf1c2dc0c81c60476233</id>
<content type='text'>
An ifdef in drm.h expects to be compiled with full-fledged Linux
toolchain, but it's common to compile kernel with just bare-metal
toolchain which doesn't define __linux__. So, also add __KERNEL__
check.

[nm@ti.com: port forward to 3.9-rc6 and post to dri devel for feedback as RFC]
Signed-off-by: Paul Sokolovsky &lt;paul.sokolovsky@linaro.org&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
</feed>
