[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100114202803.GA1749@emergent.ellipticsemi.com>
Date: Thu, 14 Jan 2010 15:28:03 -0500
From: Nick Bowler <nbowler@...iptictech.com>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
airlied@...ux.ie
Subject: Re: Linux 2.6.33-rc4
On 22:18 Thu 14 Jan , Pekka Enberg wrote:
> On Thu, Jan 14, 2010 at 9:31 PM, Nick Bowler <nbowler@...iptictech.com> wrote:
> > 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",
>
> Should I try just this or combine it with Jesse's patch?
That's the only patch on top of mainline that I use -- it's been fixing
my problems since -rc1.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists