mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@elliptictech.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	airlied@linux.ie
Subject: Re: Linux 2.6.33-rc4
Date: Thu, 14 Jan 2010 14:31:18 -0500	[thread overview]
Message-ID: <20100114193118.GA1203@emergent.ellipticsemi.com> (raw)
In-Reply-To: <4B4F6D5F.10008@cs.helsinki.fi>

On 21:15 Thu 14 Jan     , Pekka Enberg wrote:
> OK, I think I am seeing a different kind of flicker now. It doesn't 
> happen anywhere as often as before (which is probably why I missed it 
> last night). The flicker is more like a flash of some other window 
> whereas the flicker before used to "shake" the screen.
> 
> Does this ring a bell?

Your symptoms sound identical to mine on my ThinkPad T500 laptop, as
described in http://bugs.freedesktop.org/show_bug.cgi?id=25809.

This is the patch I am currently applying locally which solves all my
problems.

diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
index f4b4aa2..4fb5911 100644
--- a/drivers/gpu/drm/i915/intel_lvds.c
+++ b/drivers/gpu/drm/i915/intel_lvds.c
@@ -914,7 +914,7 @@ static void intel_find_lvds_downclock(struct drm_device *dev,
 	mutex_unlock(&dev->mode_config.mutex);
 	if (temp_downclock < panel_fixed_mode->clock) {
 		/* We found the downclock for LVDS. */
-		dev_priv->lvds_downclock_avail = 1;
+		dev_priv->lvds_downclock_avail = 0;
 		dev_priv->lvds_downclock = temp_downclock;
 		DRM_DEBUG_KMS("LVDS downclock is found in EDID. "
 				"Normal clock %dKhz, downclock %dKhz\n",

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

  parent reply	other threads:[~2010-01-14 19:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  5:44 Linus Torvalds
2010-01-13 20:21 ` Linux 2.6.33-rc4, boot regression still exists Gene Heskett
2010-01-13 21:03 ` Linux 2.6.33-rc4 Pekka Enberg
2010-01-13 21:33   ` Jesse Barnes
2010-01-13 21:50     ` Pekka Enberg
2010-01-14  0:55       ` Jesse Barnes
2010-01-14 19:15         ` Pekka Enberg
2010-01-14 19:26           ` Jesse Barnes
2010-01-14 19:31           ` Nick Bowler [this message]
2010-01-14 20:18             ` Pekka Enberg
2010-01-14 20:28               ` Nick Bowler
2010-01-14 20:48                 ` [PATCH] drm/i915: disable LVDS downclock by default Jesse Barnes
2010-01-14 20:58                   ` [Intel-gfx] " Peter Clifton
2010-01-14 21:05                     ` Linus Torvalds
2010-01-14 21:21                       ` Jesse Barnes
2010-01-14 21:16                     ` Nick Bowler
2010-01-14 21:27                       ` Jesse Barnes
2010-01-14 21:25                   ` Pekka Enberg
2010-01-14 21:51                     ` Jesse Barnes
2010-01-15  1:15                   ` Nick Bowler
2010-01-15  8:54                     ` Pekka Enberg
2010-01-15 16:14                       ` Thomas Meyer
2010-01-15 16:21                         ` Pekka Enberg
2010-01-15 16:32                         ` Nick Bowler
2010-01-15 16:46                           ` Linus Torvalds

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=20100114193118.GA1203@emergent.ellipticsemi.com \
    --to=nbowler@elliptictech.com \
    --cc=airlied@linux.ie \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.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®