From: "François Valenduc" <francois.valenduc@tvcablenet.be>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Jeff Chua <jeff.chua.linux@gmail.com>,
Alex Riesen <raa.lkml@gmail.com>
Subject: Re: Linux 2.6.37-rc8 (no fb)
Date: Wed, 29 Dec 2010 21:51:31 +0100 [thread overview]
Message-ID: <4D1B9F53.4000004@tvcablenet.be> (raw)
In-Reply-To: <20101229121601.179983b7@jbarnes-desktop>
Le 29/12/10 21:16, Jesse Barnes a écrit :
> On Wed, 29 Dec 2010 11:40:04 -0800
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> On Wed, Dec 29, 2010 at 10:21 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>>
>>> The only significant difference that I can see in the kernel message log
>>> is this:
>>
>> Hmm. I suspect that difference should have gone away with commit
>> 92971021c6328 (Revert "drm: Don't try and disable an encoder that was
>> never enabled"), but clearly that didn't fix your blank screen.
>>
>> Does reverting commit 448f53a1ede54eb854d036abf54573281412d650
>> ("drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks") fix it for
>> you? It does for some people..
>>
>> Chris - why did that lvds_ssc_freq thing suddenly start mattering? Can
>> we please just disable spread-spectrum entirely? Or perhaps only if we
>> notice that it was enabled already? Or something?
>
> Randy, Jeff and Alex, does the below help at all? If so, it may be the
> minimal fix we want for 2.6.37.
>
> diff --git a/drivers/gpu/drm/i915/intel_bios.c b/drivers/gpu/drm/i915/intel_bios
> index 2b20786..d27d016 100644
> --- a/drivers/gpu/drm/i915/intel_bios.c
> +++ b/drivers/gpu/drm/i915/intel_bios.c
> @@ -263,6 +263,9 @@ parse_general_features(struct drm_i915_private *dev_priv,
> dev_priv->int_tv_support = general->int_tv_support;
> dev_priv->int_crt_support = general->int_crt_support;
> dev_priv->lvds_use_ssc = general->enable_ssc;
> + /* force disable until we can parse this correctly */
> + if (IS_GEN5(dev) || IS_GEN6(dev))
> + dev_priv->lvds_use_ssc = 0;
>
> if (dev_priv->lvds_use_ssc) {
> if (IS_I85X(dev))
>
>
I also encountered the black screen problem after commit 448f53a1. I can
confirm that the above patch solves the problem.
François Valenduc
next prev parent reply other threads:[~2010-12-29 20:58 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 1:18 Linux 2.6.37-rc8 Linus Torvalds
2010-12-29 11:18 ` Borislav Petkov
2010-12-29 12:08 ` Rafael J. Wysocki
2010-12-30 1:17 ` Zhang Rui
2010-12-29 18:21 ` Linux 2.6.37-rc8 (no fb) Randy Dunlap
2010-12-29 19:40 ` Linus Torvalds
2010-12-29 20:16 ` Jesse Barnes
2010-12-29 20:51 ` François Valenduc [this message]
2010-12-29 21:11 ` Alex Riesen
2010-12-29 21:18 ` Jesse Barnes
2010-12-29 21:53 ` Jesse Barnes
2010-12-29 23:09 ` Alex Riesen
2010-12-29 23:13 ` Jesse Barnes
2010-12-29 23:20 ` Alex Riesen
2010-12-29 23:35 ` Alex Riesen
2010-12-30 0:02 ` Jesse Barnes
2010-12-30 0:10 ` Alex Riesen
2010-12-29 22:02 ` Alex Riesen
2010-12-29 22:12 ` Randy Dunlap
2010-12-29 22:46 ` Jesse Barnes
2010-12-29 23:40 ` Randy Dunlap
2010-12-30 18:36 ` Chris Wilson
2010-12-30 17:14 ` still nfs problems [Was: Linux 2.6.37-rc8] Uwe Kleine-König
2010-12-30 17:57 ` Linus Torvalds
2010-12-30 18:24 ` Trond Myklebust
2010-12-30 18:50 ` Linus Torvalds
2010-12-30 19:25 ` Trond Myklebust
2010-12-30 20:02 ` Linus Torvalds
2010-12-30 17:59 ` Trond Myklebust
2010-12-30 19:18 ` Uwe Kleine-König
2011-01-03 21:38 ` Uwe Kleine-König
2011-01-04 0:22 ` Trond Myklebust
2011-01-05 8:40 ` Uwe Kleine-König
2011-01-05 11:05 ` Uwe Kleine-König
2011-01-05 11:27 ` Russell King - ARM Linux
2011-01-05 12:14 ` Marc Kleine-Budde
2011-01-05 13:02 ` Nori, Sekhar
2011-01-05 15:34 ` Russell King - ARM Linux
2011-01-05 13:40 ` Uwe Kleine-König
2011-01-05 14:29 ` Jim Rees
2011-01-05 14:42 ` Marc Kleine-Budde
2011-01-05 15:38 ` Jim Rees
2011-01-05 14:53 ` Trond Myklebust
2011-01-05 15:01 ` Marc Kleine-Budde
2011-01-05 15:14 ` Trond Myklebust
2011-01-05 15:29 ` Trond Myklebust
2011-01-05 15:39 ` Marc Kleine-Budde
2011-01-05 15:52 ` Russell King - ARM Linux
2011-01-05 17:17 ` Trond Myklebust
2011-01-05 17:26 ` Russell King - ARM Linux
2011-01-05 18:12 ` Trond Myklebust
2011-01-05 18:27 ` Russell King - ARM Linux
2011-01-05 18:55 ` Trond Myklebust
2011-01-05 19:07 ` Russell King - ARM Linux
2011-01-14 2:25 ` Andy Isaacson
2011-01-14 2:40 ` Trond Myklebust
2011-01-14 4:22 ` Andy Isaacson
2011-01-03 8:48 ` Linux 2.6.37-rc8 Domenico Andreoli
2011-01-04 14:26 ` Pavel Machek
2011-01-04 14:35 ` Chris Wilson
2011-01-04 21:04 ` Pavel Machek
2011-01-04 21:15 ` Dave Airlie
2011-01-05 7:21 ` Pavel Machek
2011-01-05 22:05 ` Pavel Machek
2011-01-05 22:49 ` Dave Airlie
2011-01-06 20:27 ` Pavel Machek
2000-01-01 0:13 ` Pavel Machek
2011-01-08 12:46 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2010-12-30 2:49 Linux 2.6.37-rc8 (no fb) Jeff Chua
2010-12-30 18:16 ` Jesse Barnes
2010-12-30 23:31 ` Chris Wilson
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=4D1B9F53.4000004@tvcablenet.be \
--to=francois.valenduc@tvcablenet.be \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=randy.dunlap@oracle.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