From: Theodore Tso <tytso@mit.edu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
Eric Anholt <eric@anholt.net>,
linux-kernel@vger.kernel.org, Keith Packard <keithp@keithp.com>
Subject: Re: 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops
Date: Mon, 12 Oct 2009 22:31:46 -0400 [thread overview]
Message-ID: <20091013023146.GA8414@mit.edu> (raw)
In-Reply-To: <20091012120510.16bd1194@jbarnes-g45>
On Mon, Oct 12, 2009 at 12:05:10PM -0700, Jesse Barnes wrote:
> On Mon, 12 Oct 2009 20:46:51 +0200
> "Carlos R. Mafra" <crmafra2@gmail.com> wrote:
>
> > On Mon 12.Oct'09 at 9:54:38 -0700, Jesse Barnes wrote:
> > > >
> > > > Nope, unfortunately, it's not helping on my T400 laptop. I'm
> > > > still getting huge amounts of glitching and tearing with this
> > > > patch applied against -rc3.
> > > >
> > > > What I'm using for now to fix up my system is this patch.
> > > >
> > >
> > > How about this one? I have one more idea to try out if this doesn't
> > > work (hacking on it now).
> >
> > I was also experiencing something very similar to Theodore's bug
> > report and, at least for me, the patch below fixed the issue (the
> > previous one also had no effect).
>
> Cool, good to hear. Hopefully Ted and Keith will confirm too.
Hmm, the amount of tearing seems to be a bit less frequent, but it's
definitely still happening with this patch applied. Sorry....
- Ted
> --
> Jesse Barnes, Intel Open Source Technology Center
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 7a5fb79..1451945 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -1047,7 +1047,7 @@ static void g4x_enable_fbc(struct drm_crtc *crtc, unsigned long interval)
> dev_priv->cfb_fence = obj_priv->fence_reg;
> dev_priv->cfb_plane = intel_crtc->plane;
>
> - dpfc_ctl = plane | DPFC_SR_EN | DPFC_CTL_LIMIT_1X;
> + dpfc_ctl = plane | DPFC_CTL_LIMIT_1X;
> if (obj_priv->tiling_mode != I915_TILING_NONE) {
> dpfc_ctl |= DPFC_CTL_FENCE_EN | dev_priv->cfb_fence;
> I915_WRITE(DPFC_CHICKEN, DPFC_HT_MODIFY);
next prev parent reply other threads:[~2009-10-13 2:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 22:40 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops Theodore Ts'o
2009-10-02 22:44 ` Jesse Barnes
2009-10-04 13:43 ` Arkadiusz Miskiewicz
2009-10-05 20:47 ` Jesse Barnes
2009-10-08 17:36 ` Jesse Barnes
2009-10-10 20:41 ` Theodore Tso
2009-10-12 16:54 ` Jesse Barnes
2009-10-12 18:46 ` Carlos R. Mafra
2009-10-12 19:05 ` Jesse Barnes
2009-10-13 2:31 ` Theodore Tso [this message]
2009-10-13 17:01 ` Jesse Barnes
2009-10-13 19:00 ` Theodore Tso
2009-10-13 19:14 ` Jesse Barnes
2009-10-14 21:22 ` Jesse Barnes
2009-10-15 2:26 ` Theodore Tso
2009-10-15 4:02 ` Theodore Tso
2009-10-19 1:04 ` Jesse Barnes
2009-10-19 1:15 ` Jesse Barnes
2009-10-21 4:48 ` Theodore Tso
2009-10-26 7:25 ` Paul Rolland
2009-10-27 16:37 ` Johan Hovold
2009-10-15 15:30 ` Jesse Barnes
2009-10-15 1:23 ` Theodore Tso
2009-10-13 19:19 ` Fabio Comolli
2009-10-13 19:25 ` Jesse Barnes
2009-10-13 20:03 ` Fabio Comolli
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=20091013023146.GA8414@mit.edu \
--to=tytso@mit.edu \
--cc=crmafra2@gmail.com \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.