[PATCH 1/3] Extract the EDID blob when adding a DRM output

Richard Hughes hughsient at gmail.com
Tue Apr 23 01:59:33 PDT 2013


On 23 April 2013 08:32, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> Client side parsing is a different issue indeed. However the patch author
> mentioned in the initial post GNOME CMS alias colord as a plugin inside the
> Weston CMS. So other possible CMS plugins like Argyll and Oyranos have
> different requirements and want to access the standards EDID binary blob for
> their own feature set.

You mean things like the Yxy primaries and the MD5 ID? That's
perfectly in scope for my little parser here, I just didn't include it
yet as I wanted to get the core stuff implemented and reviewed.

> Btw. a library for parsing CMS related attributes from EDID exists:
> http://www.oyranos.org/libxcm/

Sure, but it's an additional dep, which also drags in quite a few
chunks of the weirder parts of X11. We don't need a deps list like
that just to parse a few fields in an EDID blob.

Richard.


More information about the wayland-devel mailing list