Hi,
Just replying to Drew's mail since it's the most substantive. It seems
like things have petered out a fair bit. Having someone write up a
strawman CONTRIBUTING doc would be great. I'd love to do that myself,
but have been travelling this week (& on holiday for the next few
days), so not sure wh
On Thu, Mar 7, 2019 at 2:35 PM Graeme Gill wrote:
>
> Michel Dänzer wrote:
>
> > It sounds like KMS leases could be a pretty good fit for a calibration
> > application. It can lease each output individually from the Wayland
> > compositor and fully control it using KMS APIs, while the Wayland
> >
Michel Dänzer wrote:
> It sounds like KMS leases could be a pretty good fit for a calibration
> application. It can lease each output individually from the Wayland
> compositor and fully control it using KMS APIs, while the Wayland
> compositor continues running normally on other outputs.
There s
Michel Dänzer wrote:
> Yep. The alternative is that the different mechanisms clobber the
> hardware LUT from each other, which sucks from a user POV.
Which user though ?
It certainly does the opposite of suck if you are a user
who wants reliable color management, and so want a simple
and direct
Kai-Uwe wrote:
Hi,
> Device links are a serialisation of a color transform. lcms supports to
> dump color transforms to device links and load a device link into a
> color transform. Device link profiles come with little effort. Device
> links provide applications a entry to let the compositor do
Michel Dänzer wrote:
> As of xserver 1.19, if the Xorg driver calls xf86HandleColormaps(), all
> relevant mappings (colormap, global gamma, xf86VidMode per-X-screen
> ramp, RandR per-CRTC ramp) are composed, and the result is applied to
> the hardware LUT for all CRTCs.
It's disappointing a chang
Chris Murphy wrote:
Hi Chris,
> Not every desktop environment is using the same Wayland compositor, or
> even a Wayland compositor at all. So is drm/kms something you can
> depend on most of the time regardless of the desktop?
I'm sure you could get even wider coverage of color management
tools
On Wed, 2019-03-06 at 18:09 +0100, Sebastian Wick wrote:
> 2. How exactly should the client be informed of the "prefered" color
>spaces?
>IMO there are a few requirements:
>* the client should know when the prefered color space changes
>* the client should know when multiple color
On Thu, Mar 7, 2019 at 3:15 AM Michel Dänzer wrote:
>
> On 2019-03-07 8:05 a.m., Chris Murphy wrote:
> > Of course. It can take 5-30 minutes to do a calibration and
> > characterization. In particular if I have 2, 3 or even 4 displays
> > connected I'd want to calibrate them in sequence while the
On 2019-03-07 1:43 p.m., Kai-Uwe wrote:
> Am 07.03.19 um 11:15 schrieb Michel Dänzer:
>> On 2019-03-07 8:05 a.m., Chris Murphy wrote:
>>> On Wed, Mar 6, 2019 at 10:02 PM Graeme Gill wrote:
[ And why should Linux/Wayland be crippled compared to
every other system ? I can and do do thing
Hi all,
it has been over a week since the proposal, it got 5 acks and no
objections, so I went ahead.
I have just enabled merge requests on the wayland repository and solved
https://gitlab.freedesktop.org/wayland/wayland/issues/49 .
Just like with Weston, we will continue draining the patches fr
Am 07.03.19 um 11:15 schrieb Michel Dänzer:
> On 2019-03-07 8:05 a.m., Chris Murphy wrote:
>> On Wed, Mar 6, 2019 at 10:02 PM Graeme Gill wrote:
>>> [ And why should Linux/Wayland be crippled compared to
>>> every other system ? I can and do do things like fire up
>>> a test patch display usin
On Wed, 6 Mar 2019 07:33:01 -0600
Derek Foreman wrote:
> On Wed, 6 Mar 2019 at 04:49, Ray, Ian (GE Healthcare) wrote:
> >
> >
> >
> > > On 6 Mar 2019, at 11.28, Pekka Paalanen wrote:
> > >
> > > Going once, going twice...
> > >
> > > Any objections? More acks?
>
> Acked-by: Derek Foreman
Am 07.03.2019 um 05:26 schrieb Chris Murphy:
> Hmmm. For a while now we've had display calibration+profiling
> applications compel full screen mode
While some calibration/profiing applications are able to display a
fullscreen window for the patch area (some may even default to it), I
know none tha
Wed Mar 6 17:09:27 UTC 2019 Sebastian Wick :
>...
> 2. The whole pipeline should look something like
>
> [surface cs] -cs conversion-> [output cs] -tone mapping-> [output cs]
>-degamma-> [output linear cs] -blending-> [output linear cs] -gamma->
>[output cs].
>
>Where some parts can
Thu Mar 7 08:37:11 UTC 2019 Kai-Uwe
> Am 06.03.19 um 18:09 schrieb Sebastian Wick:
> ...
>> Which brings me to open issues:
>>
>> 1. Does it make sense to support device link profiles? I'm against it
>>but would love to hear if anyone has objections given that they are
>>supported in the ot
Regards
Shashank
> -Original Message-
> From: Graeme Gill [mailto:grae...@argyllcms.com]
> Sent: Thursday, March 7, 2019 7:05 AM
> To: Sharma, Shashank ; gra...@argyllcms.com;
> Pekka Paalanen ; Nautiyal, Ankit K
>
> Cc: e.bur...@gmail.com; Kps, Harish Krupo ;
> niels_...@salscheider-onli
On 2019-03-07 8:05 a.m., Chris Murphy wrote:
> On Wed, Mar 6, 2019 at 10:02 PM Graeme Gill wrote:
>>
>> Chris Murphy wrote:
>>
>>> Hmmm. For a while now we've had display calibration+profiling
>>> applications compel full screen mode so they're not really usable
>>> alongside anything else. They a
On 2019-03-07 5:38 a.m., Graeme Gill wrote:
> Michel Dänzer wrote:
>> As of xserver 1.19, if the Xorg driver calls xf86HandleColormaps(), all
>> relevant mappings (colormap, global gamma, xf86VidMode per-X-screen
>> ramp, RandR per-CRTC ramp) are composed, and the result is applied to
>> the hardwa
On Wed, 6 Mar 2019 15:54:31 -0500
Chris Billington wrote:
> The definition of wl_argument in wayland-util.h references wl_object,
> so wl_object ought to be defined in wayland-util.h. This resolves
> gitlab issue #78.
> ---
> src/wayland-util.h | 14 ++
> 1 file changed, 14 insertio
On Wed, 2019-03-06 at 18:09 +0100, Sebastian Wick wrote:
[...]
> 4. How do universal planes handle gamma when blending? This hopefully
>has a sinmple answer and there probably is some documention which
>I just can't find.
I think they currently don't, and it will depend on the driver. Ther
Am 06.03.19 um 18:09 schrieb Sebastian Wick:
> Sending in v2 with small fixes only. I'm using this in the hope to focus
> the previous discussion in the direction of the actual protocol and
> implementation.
>
> It looks like we have come to at least some consensus on a few points.
> If anyone disa
Am 07.03.19 um 02:47 schrieb Graeme Gill:
> Niels Ole Salscheider wrote:
>
> Hi,
>
>> We added the device link profiles for "professional" applications that want
>> to
>> have full control.
> Right, but with the availability of wl_surface.enter/leave events, the
> client can keep track of which
23 matches
Mail list logo
