From: Keith Packard <keithp@keithp.com>
To: Melchior FRANZ <melchior.franz@gmail.com>, linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org
Subject: [PATCH] Revert "drm/i915: Only enable the plane after setting the fb base (pre-ILK)"
Date: Thu, 12 May 2011 11:52:29 -0700 [thread overview]
Message-ID: <yun39kjah02.fsf@aiko.keithp.com> (raw)
In-Reply-To: <201105121849.09225@rk-nord.at>
[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]
This reverts commit 49183b2818de6899383bb82bc032f9344d6791ff.
Franz Melchior:
This patch introduces a bug on my infamous "Acer Travelmate
5735Z-452G32Mnss": when KMS takes over, the frame buffer contents
get completely garbled up on screen, with colored stripes and
unreadable text (photo on request). Only when X11 is started, the
screen gets restored again. Closing and re-opening the lid partly
cures the mess, too: it makes the font readable, though horizontally
stretched.
---
On Thu, 12 May 2011 18:49:08 +0200, Melchior FRANZ <melchior.franz@gmail.com> wrote:
> * Linus Torvalds -- Tuesday 10 May 2011:
> > But please do test, just to make sure that 39-final is good.
>
> > Chris Wilson (4):
> > drm/i915: Only enable the plane after setting the fb base (pre-ILK)
>
> This patch introduces a bug on my infamous "Acer Travelmate
> 5735Z-452G32Mnss": when KMS takes over, the frame buffer contents
> get completely garbled up on screen, with colored stripes and
> unreadable text (photo on request). Only when X11 is started, the
> screen gets restored again. Closing and re-opening the lid partly
> cures the mess, too: it makes the font readable, though horizontally
> stretched.
>
> Reverting 49183b2818de6899383bb82bc032f9344d6791ff fixes the
> bug.
It's Whack-a-Mole time! Fix one laptop, break another. We'll pick 'no
regressions' over 'fixes existing bug' today.
drivers/gpu/drm/i915/intel_display.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 373c2a0..2166ee0 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -5154,6 +5154,8 @@ static int intel_crtc_mode_set(struct drm_crtc *crtc,
I915_WRITE(DSPCNTR(plane), dspcntr);
POSTING_READ(DSPCNTR(plane));
+ if (!HAS_PCH_SPLIT(dev))
+ intel_enable_plane(dev_priv, plane, pipe);
ret = intel_pipe_set_base(crtc, x, y, old_fb);
--
1.7.5.1
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-05-12 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 2:49 Linux 2.6.39-rc7 Linus Torvalds
2011-05-10 3:53 ` Konrad Rzeszutek Wilk
2011-05-10 23:36 ` Konrad Rzeszutek Wilk
2011-05-10 23:42 ` H. Peter Anvin
2011-05-12 16:49 ` [2.6.39 regression] i915/kms: garbled screen because of 49183b281 (was: Re: Linux 2.6.39-rc7) Melchior FRANZ
2011-05-12 18:52 ` Keith Packard [this message]
2011-05-12 21:41 ` Chris Wilson
2011-05-13 11:59 ` Melchior FRANZ
2011-05-30 12:10 ` [3.0-rc1 regression] (was: Re: [2.6.39 regression] i915/kms: garbled screen because of 49183b281) Melchior FRANZ
2011-05-15 13:50 ` Linux 2.6.39-rc7 Borislav Petkov
2011-05-15 13:53 ` Tejun Heo
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=yun39kjah02.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=melchior.franz@gmail.com \
--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