Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-29 Thread Daniel Vetter
On Mon, May 28, 2018 at 03:26:48PM +0200, Noralf Trønnes wrote: > > Den 24.05.2018 10.42, skrev Daniel Vetter: > > On Wed, May 23, 2018 at 04:34:06PM +0200, Noralf Trønnes wrote: > > > This the beginning of an API for in-kernel clients. > > > First out is a way to get a framebuffer backed by a dum

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-28 Thread Noralf Trønnes
Den 24.05.2018 10.42, skrev Daniel Vetter: On Wed, May 23, 2018 at 04:34:06PM +0200, Noralf Trønnes wrote: This the beginning of an API for in-kernel clients. First out is a way to get a framebuffer backed by a dumb buffer. Only GEM drivers are supported. The original idea of using an exported

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-24 Thread Thomas Hellstrom
On 05/24/2018 12:14 PM, Daniel Vetter wrote: On Thu, May 24, 2018 at 11:25:04AM +0200, Thomas Hellstrom wrote: On 05/24/2018 10:32 AM, Daniel Vetter wrote: On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote: Hi, Noralf. A couple of issues below: On 05/23/2018 04:34 PM, Noralf T

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-24 Thread Daniel Vetter
On Thu, May 24, 2018 at 11:25:04AM +0200, Thomas Hellstrom wrote: > On 05/24/2018 10:32 AM, Daniel Vetter wrote: > > On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote: > > > Hi, Noralf. > > > > > > A couple of issues below: > > > > > > On 05/23/2018 04:34 PM, Noralf Trønnes wrote:

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-24 Thread Thomas Hellstrom
On 05/24/2018 10:32 AM, Daniel Vetter wrote: On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote: Hi, Noralf. A couple of issues below: On 05/23/2018 04:34 PM, Noralf Trønnes wrote: This the beginning of an API for in-kernel clients. First out is a way to get a framebuffer backed

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-24 Thread Daniel Vetter
On Wed, May 23, 2018 at 04:34:06PM +0200, Noralf Trønnes wrote: > This the beginning of an API for in-kernel clients. > First out is a way to get a framebuffer backed by a dumb buffer. > > Only GEM drivers are supported. > The original idea of using an exported dma-buf was dropped because it > als

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-24 Thread Daniel Vetter
On Wed, May 23, 2018 at 11:45:00PM +0200, Thomas Hellstrom wrote: > Hi, Noralf. > > A couple of issues below: > > On 05/23/2018 04:34 PM, Noralf Trønnes wrote: > > This the beginning of an API for in-kernel clients. > > First out is a way to get a framebuffer backed by a dumb buffer. > > > > Onl

Re: [PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-23 Thread Thomas Hellstrom
Hi, Noralf. A couple of issues below: On 05/23/2018 04:34 PM, Noralf Trønnes wrote: This the beginning of an API for in-kernel clients. First out is a way to get a framebuffer backed by a dumb buffer. Only GEM drivers are supported. The original idea of using an exported dma-buf was dropped be

[PATCH 4/9] drm: Begin an API for in-kernel clients

2018-05-23 Thread Noralf Trønnes
This the beginning of an API for in-kernel clients. First out is a way to get a framebuffer backed by a dumb buffer. Only GEM drivers are supported. The original idea of using an exported dma-buf was dropped because it also creates an anonomous file descriptor which doesn't work when the buffer is