Re: [PATCH v2] drm: Allow CAP_DUMB_BUFFERS on !MODESET

2018-05-09 Thread Daniel Vetter
On Tue, May 08, 2018 at 08:42:03PM -0300, Ezequiel Garcia wrote: > Hey Daniel, > > On Tue, 2018-05-08 at 09:55 +0200, Daniel Vetter wrote: > > On Tue, May 08, 2018 at 01:52:01AM -0300, Ezequiel Garcia wrote: > > > It's perfectly possible to get dumb buffers out of drivers > > > that don't support

Re: [PATCH v2] drm: Allow CAP_DUMB_BUFFERS on !MODESET

2018-05-09 Thread Ezequiel Garcia
Hey Daniel, On Tue, 2018-05-08 at 09:55 +0200, Daniel Vetter wrote: > On Tue, May 08, 2018 at 01:52:01AM -0300, Ezequiel Garcia wrote: > > It's perfectly possible to get dumb buffers out of drivers > > that don't support modeset. This is the case of vgem, > > which can be used to export dmabuf to

Re: [PATCH v2] drm: Allow CAP_DUMB_BUFFERS on !MODESET

2018-05-08 Thread Daniel Vetter
On Tue, May 08, 2018 at 01:52:01AM -0300, Ezequiel Garcia wrote: > It's perfectly possible to get dumb buffers out of drivers > that don't support modeset. This is the case of vgem, > which can be used to export dmabuf to run various tests. > > Inspired by commit f3f4c4d68a28 ("drm: Allow CAP_PRIM

[PATCH v2] drm: Allow CAP_DUMB_BUFFERS on !MODESET

2018-05-08 Thread Ezequiel Garcia
It's perfectly possible to get dumb buffers out of drivers that don't support modeset. This is the case of vgem, which can be used to export dmabuf to run various tests. Inspired by commit f3f4c4d68a28 ("drm: Allow CAP_PRIME on !MODESET"). Fixes: d5264ed3823a ("drm: Return -ENOTSUPP when called f