From: "Keith Packard" <keithp@keithp.com>
To: "Torvalds\, Linus" <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Airlie, Dave" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: [PULL] drm intel fixes
Date: Thu, 21 Apr 2011 08:52:09 -0700 [thread overview]
Message-ID: <yun7hanzjo6.fsf@aiko.keithp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
Here's a couple of minor fixes for intel modesetting.
These should resolve the following bugs:
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=35977
References: https://bugs.freedesktop.org/show_bug.cgi?id=35903
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=35796
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=32612
These didn't uncover any regressions in testing compared with -rc2. We
have found an S4 resume regression in -rc2 compared with .38 on the
Piketon platform which we're still chasing.
the following changes since commit 6221f222c0ebf1acdf7abcf927178f40e1a65e2a:
Linux 2.6.39-rc2 (2011-04-05 18:30:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux-2.6.git drm-intel-fixes
Chris Wilson (2):
drm/i915: Sanitize the output registers after resume
drm/i915: Initialise g4x watermarks for disabled pipes
Mathew McKernan (2):
drm/i915/tv: Remember the detected TV type
drm/i915/tv: Only poll for TV connections
Sitsofe Wheeler (1):
drm/i915/tv: Fix modeset flickering introduced in 7f58aabc3
drivers/gpu/drm/i915/intel_display.c | 73 ++++++++++++++++++---------------
drivers/gpu/drm/i915/intel_tv.c | 9 ++--
2 files changed, 45 insertions(+), 37 deletions(-)
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2011-04-21 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 15:52 Keith Packard [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-09 23:51 [PULL] drm intel fixes Keith Packard
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=yun7hanzjo6.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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