From: Jon Masters <jonathan@jonmasters.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [bisected] offset display bug in i915
Date: Mon, 08 Nov 2010 05:18:32 -0500 [thread overview]
Message-ID: <1289211512.3916.383.camel@constitution.bos.jonmasters.org> (raw)
Hi Chris,
The following patch that you recently committed breaks my ASUS Eee PC
1015PEM by causing the display to be offset by about 1 inch (a few
centimeters) when the mode is (re)set during boot. I previously posted
both photographs and video of the problem in another "PROBLEM" thread.
Here is the offending commit found through bisection:
219adae138513bae20b256f1946b9cb3b75ca05c is the first bad commit
commit 219adae138513bae20b256f1946b9cb3b75ca05c
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Thu Sep 16 23:05:10 2010 +0100
drm/i915: Cache LVDS EDID
We assume that the panel is permenantly connected and that the EDID
data is consistent from boot, so simply cache the whole EDID for the
panel.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
I'll look at the patch. Either the EDID is *not* consistent (in which
case, why are we not seeing other bugs like this?) or there is something
specific to this system or panel used.
Jon.
next reply other threads:[~2010-11-08 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 10:18 Jon Masters [this message]
2010-11-08 10:20 ` [bisected] offset display bug in i915 Jon Masters
2010-11-08 10:27 ` Chris Wilson
2010-11-08 10:54 ` Jon Masters
2010-11-08 11:22 ` 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:23 ` [OT] avoid preformatting in Evolution (was: [bisected] offset display bug in i915) Paul Menzel
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=1289211512.3916.383.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--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