Re: [question] can multiple compositor share surfaces

2019-05-21 Thread Simon Ser
On Tuesday, May 21, 2019 6:56 PM, Damian Ivanov wrote: > Hello Simon, > > I imagine many possible usecases for example: > Two compositors, one crashes the surfaces are not deleted and you are > logged out to your gdm/sddm login vt, but the other compositor takes > ownership of the surfaces and sta

Re: [RFC PATCH v2 0/1] Color manager calibration protocol

2019-05-21 Thread Erwin Burema
On Tue, 21 May 2019 at 21:07, Sebastian Wick wrote: > > On 2019-05-21 19:32, Erwin Burema wrote: > > Hi, > > > > This is the second version of my color manager calibration protocol, > > biggest change is that I now use a surface this surface is set up in a > > similar way to the touch screen calib

Re: [RFC PATCH v2 0/1] Color manager calibration protocol

2019-05-21 Thread Sebastian Wick
On 2019-05-21 19:32, Erwin Burema wrote: Hi, This is the second version of my color manager calibration protocol, biggest change is that I now use a surface this surface is set up in a similar way to the touch screen calibration protocol. Another big change is more (and hopefully better) documen

[RFC PATCH v2 1/1] Adding color calibration protocol

2019-05-21 Thread Erwin Burema
--- .../wp_wayland_calibration.xml| 247 ++ 1 file changed, 247 insertions(+) create mode 100644 unstable/color_calibration/wp_wayland_calibration.xml diff --git a/unstable/color_calibration/wp_wayland_calibration.xml b/unstable/color_calibration/wp_wayland_calib

[RFC PATCH v2 0/1] Color manager calibration protocol

2019-05-21 Thread Erwin Burema
Hi, This is the second version of my color manager calibration protocol, biggest change is that I now use a surface this surface is set up in a similar way to the touch screen calibration protocol. Another big change is more (and hopefully better) documentation and the last big one is a new way

Re: [question] can multiple compositor share surfaces

2019-05-21 Thread Damian Ivanov
Hello Simon, I imagine many possible usecases for example: Two compositors, one crashes the surfaces are not deleted and you are logged out to your gdm/sddm login vt, but the other compositor takes ownership of the surfaces and starts another 'backup compositor' or another example would be an alte

Re: [question] can multiple compositor share surfaces

2019-05-21 Thread Simon Ser
On Tuesday, May 21, 2019 2:44 PM, Damian Ivanov wrote: > Hello, > > Is it possible for two separate compositors to share the same list of > surfaces or connect to the other compositor and receive the surfaces > or connect to the wayland-0 file and receive new surfaces as well? Hi, Can you explai

[question] can multiple compositor share surfaces

2019-05-21 Thread Damian Ivanov
Hello, Is it possible for two separate compositors to share the same list of surfaces or connect to the other compositor and receive the surfaces or connect to the wayland-0 file and receive new surfaces as well? Thanks in advance. ___ wayland-devel mai

Re: [PATCH] drm/doc: More fine-tuning on userspace review requirements

2019-05-21 Thread Simon Ser
On Tuesday, May 21, 2019 11:48 AM, Daniel Vetter wrote: > With Eric's patch > > commit ba6e798ecf320716780bb6a6088a8d17dcba1d49 > Author: Eric Anholt > Date: Wed Apr 24 11:56:17 2019 -0700 > > drm/doc: Document expectation that userspace review looks at kernel uAPI. > > there's been concern

Re: [PATCH] drm/doc: More fine-tuning on userspace review requirements

2019-05-21 Thread Pekka Paalanen
On Tue, 21 May 2019 10:48:49 +0200 Daniel Vetter wrote: > With Eric's patch > > commit ba6e798ecf320716780bb6a6088a8d17dcba1d49 > Author: Eric Anholt > Date: Wed Apr 24 11:56:17 2019 -0700 > > drm/doc: Document expectation that userspace review looks at kernel uAPI. > > there's been con

[PATCH] drm/doc: More fine-tuning on userspace review requirements

2019-05-21 Thread Daniel Vetter
With Eric's patch commit ba6e798ecf320716780bb6a6088a8d17dcba1d49 Author: Eric Anholt Date: Wed Apr 24 11:56:17 2019 -0700 drm/doc: Document expectation that userspace review looks at kernel uAPI. there's been concerns raised that we expect userspace people to do in-depth kernel patch rev