From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbdev: add a function to parse further EDID Detailed
Date: Wed, 20 Oct 2010 23:19:17 +0000 [thread overview]
Message-ID: <20101020161917.d0e526a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1008200847020.6103@axis700.grange>
On Wed, 20 Oct 2010 17:12:05 +0200 (CEST)
Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> Hi Erik
>
> On Fri, 20 Aug 2010, Erik Gilling wrote:
>
> > Guennadi,
> > Not sure how you're using the edid but you can get all 4 DTDs by
> > calling fb_edid_to_monspecs() then calling fb_videomode_to_var() on
> > each of the entries in monspecs.modedb. This is still lacking as
> > modern monitors/tvs can have multiple EDID blocks. My recent patch
> > [1] is a proposal for addressing that.
>
> Thanks for your reply, yes, I did switch to using fb_edid_to_monspecs(),
> which does just what I need. However, I would indeed need the extra modes
> from extended EDID blocks, so, your patch would come in handy. What's its
> status? There have been no comments and it's not in next. I would imagine,
> that at least an EXPORT_SYNBOL() and a dummy version for when
> CONFIG_FB_MODE_HELPERS is not set are missing in your patch, but otherwise
> - are there any big objections? I.e., you just need to apply something
> like the diff below. With it applied:
>
> Tested-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> Andrew, would you be taking it after the above issues are corrected?
Sure. Please cc me on the next version.
> As a TODO: are you planning to add parsing of SVDs to your E-EDID code?
next prev parent reply other threads:[~2010-10-20 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 6:48 [PATCH] fbdev: add a function to parse further EDID Detailed Timing Guennadi Liakhovetski
2010-08-20 7:23 ` [PATCH] fbdev: add a function to parse further EDID Detailed Erik Gilling
2010-10-20 15:12 ` Guennadi Liakhovetski
2010-10-20 23:19 ` Andrew Morton [this message]
2010-10-20 23:56 ` Dave Airlie
2010-10-21 8:26 ` Geert Uytterhoeven
2010-10-21 8:47 ` Dave Airlie
2010-10-21 14:08 ` Guennadi Liakhovetski
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=20101020161917.d0e526a3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev@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).