Linux Media Controller development
 help / color / mirror / Atom feed
From: Pekka Paalanen <ppaalanen@gmail.com>
To: "Sharma, Shashank" <Shashank.Sharma@amd.com>
Cc: Daniel Stone <daniel@fooishbar.org>,
	"wayland-devel@lists.freedesktop.org" 
	<wayland-devel@lists.freedesktop.org>,
	xorg-devel@lists.x.org, linux-media@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Independent EDID parsing library
Date: Thu, 29 Apr 2021 13:49:58 +0300	[thread overview]
Message-ID: <20210429134958.446ef8c6@eldfell> (raw)
In-Reply-To: <BYAPR12MB31265E45A92C468AC1660EB6F25F9@BYAPR12MB3126.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

Adding the previous list of CCs.

On Thu, 29 Apr 2021 10:32:58 +0000
"Sharma, Shashank" <Shashank.Sharma@amd.com> wrote:

> Hello Pekka, Daniel
> 
> As discussed over IRC, I have prepared the first version of the EDID parsing library, which is hosted here:
> https://github.com/contactshashanksharma/libedid/tree/master
> 
> This is a simple C library, and I have created this library keeping a compositor's context in mind, so its easy for a compositor to use it.
> There are only 2 APIs in this library:
>               - libedid_process_edid_info: Get EDID information from raw_edid, returns filled struct edid_info ptr
>               - libedid_destroy_edid_info: Free the EDID information
> 
> I have provided much information in the README file, and have also added two simple test apps, with sample EDID, to test it.
> Please have a look and let me know your opinion on this.
> 
> Regards
> Shashank


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2021-04-29 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR12MB31265E45A92C468AC1660EB6F25F9@BYAPR12MB3126.namprd12.prod.outlook.com>
2021-04-29 10:49 ` Pekka Paalanen [this message]
2021-05-06 11:00   ` Independent EDID parsing library Pekka Paalanen

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=20210429134958.446ef8c6@eldfell \
    --to=ppaalanen@gmail.com \
    --cc=Shashank.Sharma@amd.com \
    --cc=daniel@fooishbar.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox