Hi Niels, On 21 December 2016 at 11:21, Niels Ole Salscheider <[email protected]> wrote: > Maybe the solution for profiling would then be to just use KMS for fullscreen > display and bypass the compositor completely? The profiling application could > do whatever it wants to the hardware and the compositor would then restore the > proper state when it is started again...
My working view at the moment is that whatever is doing calibration should be directly in charge of the full insane complexity of the display hardware, and that even enumerating this, let alone offering control over it, is not tractable. Which leaves us with two options: the compositor runs calibration, or external calibration apps do not run under a Wayland session and just drive DRM/KMS directly. This didn't make any sense when all display drivers were Xorg components, but hey, we do have a universal API in DRM/KMS that you can write applications directly towards, so I don't see why we should bend over backwards making these compromises for special-purpose clients which by definition do not interoperate with a regular desktop environment. Cheers, Daniel _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
