HDR support in Wayland/Weston

Graeme Gill graeme2 at argyllcms.com
Thu Mar 7 20:32:10 UTC 2019

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 by writing software that talks directly to the hardware,
duplicating all the graphics and mouse drivers etc. that MSWindows/OS X/Linux
implements - but what team of people is going to write and support that,
and how convenient is it to use if you have to re-boot to run it,
and what use are the display profiles if you have no confidence that
they are valid for the graphics sub-system you actually want to use
them with, and what use are such profiles if you have no reliable way
of installing them on the system you want to use them on ?

If drm/kms is such a great application target, why is Wayland being
developed at all - why isn't every Linux application written to
talk to drm/kms ?

> Android is off on its own I suspect. What's Chrome OS using? I dunno,
> maybe that's not where you want to be? :-D

Irrelevant - they have their own design as operating systems,
and may or may not have color management API's. Android has had
no reasonable prospect of CM up to now (just like Wayland!), but
recently started to add support in its own fashion. If Chrome
follows suite, they will soon be far ahead of Wayland in this


More information about the wayland-devel mailing list