Pekka Paalanen wrote:
> I presume the measurement or calibration use case always involves
> "owning" the whole monitor, and the very specific monitor at that. That
> is, making the monitor temporarily exclusive to the app, so that
> nothing else can interfere (e.g. instant messaging notification po
Carsten Haitzler (The Rasterman) wrote:
> apps should not have exclusive access. we're re-doing the whole horrid
> "install
> colormap" thing from the x days of 256 color (or paletted/colormapped
> displays).
It's not quite the same thing in all cases.
A game doing this - yes, it's setting it u
Simon Ser wrote:
> On Monday, March 4, 2019 8:13 AM, Graeme Gill wrote:
>> 2) Implement virtual per channel LUTs, with the compositor combining them
>>together in some way, and have some means of the color management
>> applications
>>being aware when the display is being interfered with
Adam Jackson wrote:
Hi,
> X kinda has three mechanisms for this. The first one, that nobody
> really uses, is setting the colormap for a DirectColor visual.
Actually this is something I check and set to linear before
calibration & profiling in the ArgyllCMS tools.
> The
> second, which games ty
Pekka Paalanen wrote:
> The only question is, do color management and HDR support conceptually
> make sense as independent features, or would implementations always
> support both with essentially the same effort?
In my view, you can certainly add an HDR extension independently
of a color managem
Pekka Paalanen wrote:
> Sebastian's protocol proposal includes render intent from applications.
> Conversion of client content to the blending space should ideally be
> lossless, so the render intent in that step should be irrelevant if I
> understand right. How to deal with render intent when conv
Chris Murphy wrote:
> 1.0. So yeah for HDR that information is useless and is one of the
> gotchas with ICC display class profiles. There are optional tags
> defined in the spec for many years now to include measured display
> black and white luminance. For HDR applications it would seem it'd
> ha
This is the beta for the upcoming 1.17 release.
Changelog:
Derek Foreman (1):
configure.ac: bump to version 1.16.92 for the beta release
Leonid Bobrov via wayland-devel (1):
tests: fix main symbol duplication
Simon Ser (1):
protocol: warn clients about some wl_output properties
Here's the beta for the upcoming weston 6.0 release. Mostly bug/typo
fixes here, as should be the case at this point in the cycle.
Changelog:
Alexandros Frantzis (1):
clients/simple-dmabuf-egl: Create the EGL display using the GBM platform
Daniel Stone (1):
compositor-drm: Add missin
Am Mittwoch, 27. Februar 2019, 14:17:07 CET schrieb Pekka Paalanen:
> On Tue, 26 Feb 2019 18:56:06 +0100
>
> Kai-Uwe wrote:
> > Am 26.02.19 um 16:48 schrieb Pekka Paalanen:
> > > On Sun, 22 Jan 2017 13:31:35 +0100
> > >
> > > Niels Ole Salscheider wrote:
> > >> Signed-off-by: Niels Ole Salschei
On Mon, 4 Mar 2019 22:21:44 +0200
Leonid Bobrov wrote:
> You know, I think this whole patch is silly, because waitid() is part of
> POSIX, FreeBSD and NetBSD implement it while OpenBSD and DragonFly BSD
> don't. I'll ask OpenBSD upstream to merge NetBSD's implementation and
> DragonFly BSD upstre
11 matches
Mail list logo
