Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Keith Packard
Neil Armstrong writes: > Seeing the description, it seems to be a libdrm with steroids, > why libdrm doesn't handle all this already ? That'd be a lot of steroids; we're talking about creating helper functions all the way up to rendering images into scanout buffers (presumably using Vulkan?) for

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Daniel Vetter
On Tue, Oct 8, 2019 at 4:36 PM Alex Deucher wrote: > > On Tue, Oct 8, 2019 at 5:32 AM Daniel Stone wrote: > > > > Hi, > > > > On Mon, 7 Oct 2019 at 19:16, Keith Packard wrote: > > > Daniel Stone writes: > > > > I think there would be a load of value in starting with simple helpers > > > > which

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Alex Deucher
On Tue, Oct 8, 2019 at 5:32 AM Daniel Stone wrote: > > Hi, > > On Mon, 7 Oct 2019 at 19:16, Keith Packard wrote: > > Daniel Stone writes: > > > I think there would be a load of value in starting with simple helpers > > > which can be used independently of any larger scheme, tackling that > > > l

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Heinrich Fink
On Mon, 7 Oct 2019 at 20:16, Keith Packard wrote: > > Daniel Stone writes: > > > I think there would be a load of value in starting with simple helpers > > which can be used independently of any larger scheme, tackling that > > list above. > > Yeah, a helper library that didn't enforce at tonne o

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Daniel Stone
Hi, On Mon, 7 Oct 2019 at 19:16, Keith Packard wrote: > Daniel Stone writes: > > I think there would be a load of value in starting with simple helpers > > which can be used independently of any larger scheme, tackling that > > list above. > > Yeah, a helper library that didn't enforce at tonne

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Neil Armstrong
Hi, On 05/10/2019 18:09, Keith Packard wrote: > > During XDC this year, we heard a few presentations and had a lot of > hallway talk about sharing code for driving DRM/KMS for display. > > I think the general consensus is that there is enough shared > functionality between all of the various DRM

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-08 Thread Pekka Paalanen
On Mon, 07 Oct 2019 14:16:32 -0400 "Keith Packard" wrote: > Daniel Stone writes: > > > I think there would be a load of value in starting with simple helpers > > which can be used independently of any larger scheme, tackling that > > list above. > > Yeah, a helper library that didn't enforce

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-07 Thread Daniel Stone
On Mon, 7 Oct 2019 at 19:16, Keith Packard wrote: > Daniel Stone writes: > > I think there would be a load of value in starting with simple helpers > > which can be used independently of any larger scheme, tackling that > > list above. > > Yeah, a helper library that didn't enforce at tonne of po

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-07 Thread Keith Packard
Daniel Stone writes: > I think there would be a load of value in starting with simple helpers > which can be used independently of any larger scheme, tackling that > list above. Yeah, a helper library that didn't enforce at tonne of policy and just let the user glue things together on their own

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-07 Thread Daniel Stone
Hi, On Mon, 7 Oct 2019 at 18:35, Daniel Stone wrote: > There are definitely a few annoying problems which we should have > common resolution for. I'm thinking of: > - [...] Oh, and add backlight handling to that list. Cheers, Daniel ___ dri-devel ma

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-07 Thread Daniel Stone
Hi Keith, On Sat, 5 Oct 2019 at 17:16, Keith Packard wrote: > During XDC this year, we heard a few presentations and had a lot of > hallway talk about sharing code for driving DRM/KMS for display. Definitely. That would be great. > I think the general consensus is that there is enough shared >

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread Keith Packard
Robert Foss writes: > Hey Keith, > > Thanks for setting this up, and picking a descriptive project name :) > > How is liboutput going to relate to the libliftoff[1] project? We heard about libliftoff at XDC. It sounds like it does the plane selection stuff, including searching for configurations

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread Robert Foss
Hey Keith, Thanks for setting this up, and picking a descriptive project name :) How is liboutput going to relate to the libliftoff[1] project? [1] https://github.com/emersion/libliftoff Rob. On 05.10.19 18:09, Keith Packard wrote: During XDC this year, we heard a few presentations and ha

liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread "Keith Packard"
During XDC this year, we heard a few presentations and had a lot of hallway talk about sharing code for driving DRM/KMS for display. I think the general consensus is that there is enough shared functionality between all of the various DRM/KMS clients that we can start thinking about building a li