From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: [pull] drm-intel-fixes for 3.4-rc4
Date: Thu, 19 Apr 2012 15:08:27 +0200 [thread overview]
Message-ID: <20120419130827.GE4256@phenom.ffwll.local> (raw)
Hi Dave,
Just 3 fixes this time around:
- Regression fix for upscaled lvds modes on older machines, the clean-up
of our crtc timing handling from the interlaced patches screwed things
up there.
- Locking fix in lastclose, prevents an oops.
- Black panel on vt switch due to pageflip when upscaling fix for snb.
Wrt regressions from 3.4 I'm only aware of a funky report that might
implies rc6 in sometimes causing resume failures, but it's not yet clear
what's going on there.
Yours, Daniel
on vt switch
The following changes since commit e816b57a337ea3b755de72bec38c10c864f23015:
Linux 3.4-rc3 (2012-04-15 18:28:29 -0700)
are available in the git repository at:
git://people.freedesktop.org/~danvet/drm-intel drm-intel-fixes
for you to fetch changes up to 99d9acdd0c5ce970eaf8e8671c0bc4cb7c6fb0c1:
drm/i915: Do not set "Enable Panel Fitter" on SNB pageflips (2012-04-18 10:30:47 +0200)
----------------------------------------------------------------
Chris Wilson (2):
drm/i915: Hold mode_config lock whilst changing mode for lastclose()
drm/i915: Do not set "Enable Panel Fitter" on SNB pageflips
Daniel Vetter (1):
drm/i915: don't clobber the special upscaling lvds timings
drivers/gpu/drm/i915/intel_display.c | 15 ++++++++++++---
drivers/gpu/drm/i915/intel_drv.h | 4 ++++
drivers/gpu/drm/i915/intel_fb.c | 4 ++++
drivers/gpu/drm/i915/intel_lvds.c | 6 ++++++
drivers/gpu/drm/i915/intel_panel.c | 2 --
5 files changed, 26 insertions(+), 5 deletions(-)
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
reply other threads:[~2012-04-19 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120419130827.GE4256@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).