From: Pekka Paalanen <ppaalanen@gmail.com>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Shashank Sharma <contactshashanksharma@gmail.com>,
Shashank Sharma <shashank.sharma@amd.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH 1/3] edid-decode: Introduce libedid-decode wrapper
Date: Wed, 13 Apr 2022 13:40:58 +0300 [thread overview]
Message-ID: <20220413134058.07e849e3@eldfell> (raw)
In-Reply-To: <faf5be22-07a2-f928-085e-1a1e2aa01b12@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
On Tue, 8 Mar 2022 13:09:37 +0100
Hans Verkuil <hverkuil-cisco@xs4all.nl> wrote:
> Hi Shashank,
>
> There is no cover letter for this series, so I'll just reply to the
> first patch, but my comments are high-level and not specific to this
> patch.
>
> To be honest, I am not at all convinced that using edid-decode as a
> parser library is the right thing to do. It was never written with that
> in mind. The two purposes of edid-decode are to:
>
> 1) Convert the EDID to a human readable text, and
> 2) Verify if the EDID conforms to the various standards and is internally
> consistent.
>
> As a result the state information that edid-decode stores is just the
> state that it needs to check conformity across Extension Blocks and/or
> Data Blocks. Most of the parsed data is just printed to stdout and checked
> and then forgotten.
>
> I have considered if it would make sense to make a library to parse and
> store the EDID data and have edid-decode sit on top of that, but that will
> make the conformity tests much harder. It's kind of interwoven with the
> parsing and a parser library is really not interested in that anyway.
>
> I think edid-decode can function very well as a reference source for
> a real EDID parser since edid-decode is very complete, but not as a
> EDID parser library.
>
Hi all,
since this discussion, more people have joined the effort and the
consensus became to start a new project instead of pushing to
edid-decode upstream.
The new project is at
https://gitlab.freedesktop.org/emersion/libdisplay-info
where we are currently discussing what the API should look like in the
issues and merge request comments, so there is essentially no code yet.
If the project gains enough traction, I expect it will be moved into a
non-personal namespace under fd.o to live a life of its own.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-04-13 10:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 12:49 [PATCH 1/3] edid-decode: Introduce libedid-decode wrapper Shashank Sharma
2022-03-04 12:50 ` [PATCH 2/3] edid-decode: Introduce libedid-decode APIs Shashank Sharma
2022-03-07 16:11 ` Pekka Paalanen
2022-03-07 17:00 ` Shashank Sharma
2022-03-04 12:50 ` [PATCH 3/3] edid-decode: Add test utility for libedid-decode Shashank Sharma
2022-03-07 15:54 ` [PATCH 1/3] edid-decode: Introduce libedid-decode wrapper Pekka Paalanen
2022-03-07 16:48 ` Shashank Sharma
2022-03-08 11:21 ` Pekka Paalanen
2022-03-08 12:09 ` Hans Verkuil
2022-03-08 14:30 ` Pekka Paalanen
2022-03-08 16:36 ` Hans Verkuil
2022-03-09 14:09 ` Pekka Paalanen
2022-03-09 14:31 ` Sharma, Shashank
2022-03-09 15:41 ` Pekka Paalanen
2022-03-09 14:45 ` Hans Verkuil
2022-03-09 15:57 ` Pekka Paalanen
2022-03-09 16:00 ` Hans Verkuil
2022-03-10 12:52 ` Pekka Paalanen
2022-04-13 10:40 ` Pekka Paalanen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220413134058.07e849e3@eldfell \
--to=ppaalanen@gmail.com \
--cc=contactshashanksharma@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jani.nikula@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=shashank.sharma@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox