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

[Kai-Uwe Behrmann]

Am 23.04.2013 07:49, schrieb David Herrmann:
> On Apr 23, 2013 6:38 AM, "Graeme Gill" <graeme2 at argyllcms.com> wrote:
>> David Herrmann wrote:

>>> Patch 3/3 parses the blob and keeps the parsed values. Why
>>> should we keep the binary blob, too? If we need more EDID values, we
>>> simply extend the parser?
>>
>> This would seem to imply that every time a client/application needs some
>> piece of information from the EDID that hasn't been allowed for,
>> an update to the display server is needed.
>
> Please read the patch. This is a display server internal feature, clients
> aren't involved. It's about the display server parsing the EDID blob for
> its own use!
>
> If you want clients to be involved, it's a separate feature and you can
> keep the blob if you need it. But this doesn't belong in this patch.

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.

 >> I think the idea would be to have both (a minimal set of parsed
 >> information, + the blob), or relegate the parsing to a client
 >> library would be another approach, although supplying that
 >> client library by default would be a good thing, rather
 >> than leaving everyone to re-invent EDID parsing badly.

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

kind regards
Kai-Uwe