From: "Jonas Ådahl" <jadahl@gmail.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: Wed, 7 Apr 2021 14:40:26 +0200 [thread overview]
Message-ID: <YG2oOtvsHmOfBYMb@gmail.com> (raw)
In-Reply-To: <DJjftAG6WNev87c34XyXFLCHe49rJBCYdqENxfO3uHXUFJXmPerOg5LuQKAbd3D_pdO34vkWgfy9uggujNI12VE-ttglyarF5wAogYC8m3E=@emersion.fr>
On Wed, Apr 07, 2021 at 10:59:18AM +0000, Simon Ser wrote:
> FWIW, with my Sway/wlroots hat on I think this is a great idea and I'd
> definitely be interested in using such as library. A C API with no
> dependencies is pretty important from my point-of-view.
>
> I'd prefer if C++ was not used at all (and could almost be baited into
> doing the work if that were the case), but it seems that ship has
> sailed already.
The same for Mutter / GNOME, not having to maintain a EDID parser would
be great. Though personally I don't care if it's implemented in C++, C
or whatever, as long as there is a C API to use.
Jonas
>
> Simon
> _______________________________________________
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jonas Ådahl" <jadahl@gmail.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: Wed, 7 Apr 2021 14:40:26 +0200 [thread overview]
Message-ID: <YG2oOtvsHmOfBYMb@gmail.com> (raw)
In-Reply-To: <DJjftAG6WNev87c34XyXFLCHe49rJBCYdqENxfO3uHXUFJXmPerOg5LuQKAbd3D_pdO34vkWgfy9uggujNI12VE-ttglyarF5wAogYC8m3E=@emersion.fr>
On Wed, Apr 07, 2021 at 10:59:18AM +0000, Simon Ser wrote:
> FWIW, with my Sway/wlroots hat on I think this is a great idea and I'd
> definitely be interested in using such as library. A C API with no
> dependencies is pretty important from my point-of-view.
>
> I'd prefer if C++ was not used at all (and could almost be baited into
> doing the work if that were the case), but it seems that ship has
> sailed already.
The same for Mutter / GNOME, not having to maintain a EDID parser would
be great. Though personally I don't care if it's implemented in C++, C
or whatever, as long as there is a C API to use.
Jonas
>
> Simon
> _______________________________________________
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-07 12:40 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
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 [this message]
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=YG2oOtvsHmOfBYMb@gmail.com \
--to=jadahl@gmail.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=ppaalanen@gmail.com \
--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.