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

[David Herrmann]

Hi

On Apr 23, 2013 6:38 AM, "Graeme Gill" <graeme2 at argyllcms.com> wrote:
>
> David Herrmann wrote:
>
> > If you want to keep the EDID blob, could you describe a specific
> > use-case?
>
> Taking a hash of it to identify a particular display.
>
> Implementing specific workarounds for displays where
> the built in parser gives up.
>
> Dealing with extensions to the EDID standard.

We can do all this without keeping the blob, but see below...

> > 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.

Regards
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20130423/34cc479a/attachment.html>