From: Jon Masters <jonathan@jonmasters.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix LVDS fixed-mode regression from 219adae1
Date: Mon, 08 Nov 2010 19:16:08 -0500 [thread overview]
Message-ID: <1289261768.3916.434.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <1289258652-22665-1-git-send-email-chris@chris-wilson.co.uk>
On Mon, 2010-11-08 at 23:24 +0000, Chris Wilson wrote:
> Commit 219adae1 cached the EDID found during LVDS init, but in the
> process prevented the init routine from discovering the preferred
> fixed-mode for the panel. This was causing us to guess the correct mode,
> which sometimes is wide of the mark.
>
> Reported-by: Jon Masters <jonathan@jonmasters.org>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
I have tested this patch, and my LVDS panel display on this Eee PC
1015PEM is now working correctly :) Obviously I suspect others will be
affected in due course, so hopefully this can make the next 2.6.37 RC.
Please add my:
Tested-by: Jon Masters <jonathan@jonmasters.org>
To this patch also.
Jon.
next prev parent reply other threads:[~2010-11-09 0:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 10:18 [bisected] offset display bug in i915 Jon Masters
2010-11-08 10:20 ` [Intel-gfx] " Jon Masters
2010-11-08 10:27 ` Chris Wilson
2010-11-08 10:54 ` Jon Masters
2010-11-08 11:22 ` [Intel-gfx] " Jon Masters
2010-11-08 11:29 ` Jon Masters
2010-11-08 11:36 ` Jon Masters
2010-11-08 12:13 ` Chris Wilson
2010-11-08 17:58 ` Jon Masters
2010-11-08 23:08 ` Jon Masters
2010-11-08 23:24 ` [PATCH] drm/i915: Fix LVDS fixed-mode regression from 219adae1 Chris Wilson
2010-11-09 0:16 ` Jon Masters [this message]
2010-11-11 8:39 ` Jon Masters
2010-11-08 11:33 ` [bisected] offset display bug in i915 James Courtier-Dutton
2010-11-08 11:38 ` Jon Masters
2010-11-08 11:26 ` James Courtier-Dutton
2010-11-08 11:34 ` Jon Masters
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=1289261768.3916.434.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®