From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Peter Stuge <peter@stuge.se>
Cc: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>,
linux-kernel@vger.kernel.org, mjg@redhat.com, eric@anholt.net
Subject: Re: no video output after suspend after "drm/i915: force mode set at lid open time"
Date: Mon, 26 Oct 2009 09:02:34 -0700 [thread overview]
Message-ID: <20091026090234.32ae7656@jbarnes-g45> (raw)
In-Reply-To: <20091026015230.6438.qmail@stuge.se>
On Mon, 26 Oct 2009 02:52:30 +0100
Peter Stuge <peter@stuge.se> wrote:
> (Before this I tried 2.6.31.1 with KMS, but it didn't do Xv.)
>
> (Oh, and Xv performance with a83a44+1556c6 is lower than 2.6.30 nofb,
> but that's somewhat secondary. MPlayer performs worse than VLC, but
> both are worse than MPlayer with 2.6.30+2.7.1.)
>
> Can I help solve this somehow?
I posted a patch that fixed an X40 I was testing:
drm/i915: save/restore BLC histogram control reg across suspend/resume
can you give it a try and see if it works for you?
It may not be related to Riccardo's report, since the above patch isn't
really related to the lid switch problem.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-10-26 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 20:57 no video output after suspend after "drm/i915: force mode set at lid open time" Riccardo Magliocchetti
2009-10-26 1:52 ` Peter Stuge
2009-10-26 16:02 ` Jesse Barnes [this message]
2009-10-26 19:28 ` Peter Stuge
2009-10-26 19:39 ` Rafael J. Wysocki
2009-10-26 19:42 ` Peter Stuge
2009-10-26 20:00 ` Rafael J. Wysocki
2009-10-26 16:05 ` Jesse Barnes
2009-10-27 21:21 ` Riccardo Magliocchetti
2009-10-27 21:26 ` Jesse Barnes
2009-10-31 13:42 ` Riccardo Magliocchetti
2009-10-31 13:46 ` Riccardo Magliocchetti
2009-11-04 19:19 ` Jesse Barnes
2009-11-04 20:16 ` Riccardo Magliocchetti
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=20091026090234.32ae7656@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=peter@stuge.se \
--cc=riccardo.magliocchetti@gmail.com \
/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