linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K, Mythri P" <mythripk@ti.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Dave Airlie <airlied@gmail.com>,
	linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-media@vger.kernel.org
Subject: Re: [RFC PATCH] HDMI:Support for EDID parsing in kernel.
Date: Fri, 25 Mar 2011 13:46:05 +0000	[thread overview]
Message-ID: <AANLkTikQdUYYRSG1ZNesgxQG+HhDJ-PY_wpwz3Mec-3V@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103242001460.21914@axis700.grange>

Hi Gunnedi,

<snip>
>> > Dave's point is that we can't ditch the existing code without
>> > introducing a lot of risk; it would be better to start a library-ized
>> > EDID codebase from the most complete one we have already, i.e. the DRM
>> > EDID code.
>
> Does the DRM EDID-parser also process blocks beyond the first one and
> also parses SVD entries similar to what I've recently added to fbdev? Yes,
> we definitely need a common EDID parses, and maybe we'll have to collect
> various pieces from different implementations.
>
As far as I know , it does not parse SVD ,But it should not be that
difficult to add.
We could take the SVD parsing from your code . In the RFC i have
posted I parse for detailed timing and other VSDB blocks.
Also the parsing should be based on the extension type for  multiple
128 byte blocks.

Thanks and regards,
Mythri.

> Thanks
> Guennadi
>

      parent reply	other threads:[~2011-03-25 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 17:44 [RFC PATCH] HDMI:Support for EDID parsing in kernel Mythri P K
2011-03-22 17:52 ` Mauro Carvalho Chehab
2011-03-22 17:58   ` Paul Mundt
2011-03-23 13:59     ` K, Mythri P
2011-03-22 18:32 ` Alex Deucher
2011-03-23  0:46 ` Dave Airlie
2011-03-23 13:40   ` K, Mythri P
2011-03-23 15:18     ` Jesse Barnes
2011-03-24  9:52       ` K, Mythri P
2011-03-24 19:06         ` Corbin Simpson
2011-03-24 22:43           ` Florian Tobias Schandinat
2011-03-25 15:33             ` K, Mythri P
2011-03-24 19:13         ` Guennadi Liakhovetski
2011-03-24 19:22           ` Alex Deucher
2011-03-25 13:46           ` K, Mythri P [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=AANLkTikQdUYYRSG1ZNesgxQG+HhDJ-PY_wpwz3Mec-3V@mail.gmail.com \
    --to=mythripk@ti.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).