On Mon, Sep 30, 2013 at 01:41:13PM +0100, Damien Lespiau wrote:
The kernel series has been pushed to drm-intel, the libdrm patches should
follow if there isn't any objection.
Swiftly pushed.
--
Damien
___
dri-devel mailing list
v2 was:
http://lists.freedesktop.org/archives/dri-devel/2013-September/045354.html
Only one change, the stereo part for the flags is now an enum instead of being
a bit field.
The kernel series has been pushed to drm-intel, the libdrm patches should
follow if there isn't any objection.
--
On Sun, Sep 08, 2013 at 04:03:52PM +0100, Damien Lespiau wrote:
On Sun, Sep 08, 2013 at 03:46:43PM +0200, David Herrmann wrote:
The series implements SET_CAP as a per _file_ capability set, not per
master. I like it this way. Note that with SET_VERSION, we already
have a per _master_
On Fri, Sep 6, 2013 at 9:11 PM, Chris Wilson ch...@chris-wilson.co.uk wrote:
On Fri, Sep 06, 2013 at 07:57:16PM +0100, Damien Lespiau wrote:
Follow up of:
http://lists.freedesktop.org/archives/dri-devel/2012-September/028278.html
Let's try again! This time, intead of a magic connector
Hi
On Sun, Sep 8, 2013 at 1:59 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Sep 6, 2013 at 9:11 PM, Chris Wilson ch...@chris-wilson.co.uk wrote:
On Fri, Sep 06, 2013 at 07:57:16PM +0100, Damien Lespiau wrote:
Follow up of:
On Sun, Sep 08, 2013 at 03:46:43PM +0200, David Herrmann wrote:
The series implements SET_CAP as a per _file_ capability set, not per
master. I like it this way. Note that with SET_VERSION, we already
have a per _master_ capability set. Compared to SET_CAP it only allows
incremental capability
On Sun, Sep 8, 2013 at 5:03 PM, Damien Lespiau damien.lesp...@intel.com wrote:
On Sun, Sep 08, 2013 at 03:46:43PM +0200, David Herrmann wrote:
The series implements SET_CAP as a per _file_ capability set, not per
master. I like it this way. Note that with SET_VERSION, we already
have a per
Follow up of:
http://lists.freedesktop.org/archives/dri-devel/2012-September/028278.html
Let's try again! This time, intead of a magic connector property to select if
we want to return more modeinfo flags to userspace, this series introduces a
new SET_CAP ioctl.
So the flow goes as following:
On Fri, Sep 06, 2013 at 07:57:16PM +0100, Damien Lespiau wrote:
Follow up of:
http://lists.freedesktop.org/archives/dri-devel/2012-September/028278.html
Let's try again! This time, intead of a magic connector property to select if
we want to return more modeinfo flags to userspace, this