From: Jani Nikula <jani.nikula@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: xorg-devel@lists.x.org, dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org
Subject: Re: Call for an EDID parsing library
Date: Thu, 08 Apr 2021 18:28:29 +0300 [thread overview]
Message-ID: <87lf9siyn6.fsf@intel.com> (raw)
In-Reply-To: <BIyXHmd9St1ss-z2I5n6mdZZFRRBj2zhTq4eMGjlN-mmPpp_7VC2HjUyF22htq84SlVwil4LBddopV6slVnJIKWd6VcFmzVZOxSTzTpt0BY=@emersion.fr>
On Thu, 08 Apr 2021, Simon Ser <contact@emersion.fr> wrote:
> On Thursday, April 8th, 2021 at 4:58 PM, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>
>> Perhaps that should be the takeaway; try to minimize parsed data
>> where the consumer needs to know whether it originated from DisplayID or
>> EDID?
>
> So an EDID/DisplayID abstraction layer?
>
> It sounds like only an EDID and DisplayID expert could come up with a
> sane API for that. Also some metadata will only be available in one
> format and not the other.
Well, some of the data *already* comes from DisplayID extensions in the
EDID.
My point is, if you parse displayid and edid into different structures
and APIs, what will the code bases using the library end up looking
like? Not pretty? Implementing the same conditionals all over the place?
Anyway. I feel like I'm derailing this a bit, and I really don't want
that to happen. I think DisplayID is a consideration that should not be
forgotten, but it's probably not the first priority here.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: Pekka Paalanen <ppaalanen@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, xorg-devel@lists.x.org,
dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org
Subject: Re: Call for an EDID parsing library
Date: Thu, 08 Apr 2021 18:28:29 +0300 [thread overview]
Message-ID: <87lf9siyn6.fsf@intel.com> (raw)
In-Reply-To: <BIyXHmd9St1ss-z2I5n6mdZZFRRBj2zhTq4eMGjlN-mmPpp_7VC2HjUyF22htq84SlVwil4LBddopV6slVnJIKWd6VcFmzVZOxSTzTpt0BY=@emersion.fr>
On Thu, 08 Apr 2021, Simon Ser <contact@emersion.fr> wrote:
> On Thursday, April 8th, 2021 at 4:58 PM, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>
>> Perhaps that should be the takeaway; try to minimize parsed data
>> where the consumer needs to know whether it originated from DisplayID or
>> EDID?
>
> So an EDID/DisplayID abstraction layer?
>
> It sounds like only an EDID and DisplayID expert could come up with a
> sane API for that. Also some metadata will only be available in one
> format and not the other.
Well, some of the data *already* comes from DisplayID extensions in the
EDID.
My point is, if you parse displayid and edid into different structures
and APIs, what will the code bases using the library end up looking
like? Not pretty? Implementing the same conditionals all over the place?
Anyway. I feel like I'm derailing this a bit, and I really don't want
that to happen. I think DisplayID is a consideration that should not be
forgotten, but it's probably not the first priority here.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-04-08 15:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 8:44 Call for an EDID parsing library Pekka Paalanen
2021-04-07 8:44 ` Pekka Paalanen
2021-04-07 8:55 ` Carsten Haitzler
2021-04-07 8:55 ` Carsten Haitzler
2021-04-07 9:34 ` Hans Verkuil
2021-04-07 9:34 ` Hans Verkuil
2021-04-07 10:31 ` Jani Nikula
2021-04-07 10:31 ` Jani Nikula
2021-04-07 11:00 ` Hans Verkuil
2021-04-07 11:00 ` Hans Verkuil
2021-04-08 13:49 ` Jani Nikula
2021-04-08 13:49 ` Jani Nikula
2021-04-08 14:13 ` Pekka Paalanen
2021-04-08 14:13 ` Pekka Paalanen
2021-04-08 14:58 ` Jani Nikula
2021-04-08 14:58 ` Jani Nikula
2021-04-08 15:10 ` Simon Ser
2021-04-08 15:10 ` Simon Ser
2021-04-08 15:28 ` Jani Nikula [this message]
2021-04-08 15:28 ` Jani Nikula
2021-04-08 15:34 ` Simon Ser
2021-04-08 15:34 ` Simon Ser
2021-04-07 10:59 ` Simon Ser
2021-04-07 10:59 ` Simon Ser
2021-04-07 12:40 ` Jonas Ådahl
2021-04-07 12:40 ` Jonas Ådahl
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=87lf9siyn6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xorg-devel@lists.x.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.