LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Yaroslav Halchenko <lists@onerussian.com>,
James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: no backlight on radeon after recent kernel "upgrade"s
Date: Thu, 22 Feb 2007 00:34:31 +0000 [thread overview]
Message-ID: <1172104471.5790.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20070221055648.GM25659@washoe.onerussian.com>
On Wed, 2007-02-21 at 00:56 -0500, Yaroslav Halchenko wrote:
> I didn't mention 2.6.20-mm1 and got to see -mm2 so it is the one which
> Iv'e tried, but, once again, I experienced the same issue with 19-mm?
> kernels.
>
> I built 2.6.20-mm2 without backlight support
> $> grep BACKLIGH /boot/config-2.6.20-mm2
> # CONFIG_BACKLIGHT_LCD_SUPPORT is not set
> # CONFIG_FB_BACKLIGHT is not set
> # CONFIG_FB_RIVA_BACKLIGHT is not set
> # CONFIG_FB_RADEON_BACKLIGHT is not set
>
> that "eliminated" the problem. Also I can see the screen with pure
> 2.6.20 with backlight support (whatever it does since after
> loading lcd, backlight modules, my /sys/class/{lcd,backlight} are empty):
>
> *$> grep BACKLIGH /boot/config-2.6.20
> # CONFIG_FB_BACKLIGHT is not set
> CONFIG_BACKLIGHT_LCD_SUPPORT=y
> CONFIG_BACKLIGHT_CLASS_DEVICE=m
> CONFIG_BACKLIGHT_DEVICE=y
>
>
> > Also, do you normally see files under /sys/class/lcd?
> nope... after I load lcd module, no files under :-/ regardless either it
> is mm or not. But there are files under /sys/class/backlight/ for mm2
> compiled with backlight support (whenever the screen is dark as per my
> original email)
There should be no files appearing under /sys/class/lcd, so thats all
normal. There is another report with similar symptoms which also sounds
like enabling the following options are at fault:
# CONFIG_FB_RIVA_BACKLIGHT is not set
# CONFIG_FB_RADEON_BACKLIGHT is not set
I suspect these options only work on certain hardware and aren't
generic. James, any idea what hardware these do/don't work with?
Worst case, we set them to depend on PMAC_BACKLIGHT again I guess...
Richard
next prev parent reply other threads:[~2007-02-22 0:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 4:46 Yaroslav Halchenko
2007-02-19 8:04 ` Andrew Morton
2007-02-19 9:19 ` Richard Purdie
2007-02-21 5:56 ` Yaroslav Halchenko
2007-02-22 0:34 ` Richard Purdie [this message]
2007-02-22 1:07 ` James Simmons
2007-02-22 9:46 ` Richard Purdie
2007-02-22 15:18 ` James Simmons
2007-02-22 1:11 ` [Linux-fbdev-devel] " James Simmons
2007-02-22 2:09 ` Joel Becker
2007-02-22 15:55 ` James Simmons
2007-02-22 17:28 ` David Miller
2007-02-28 16:55 ` James Simmons
2007-03-01 10:57 ` Richard Purdie
2007-03-01 21:08 ` James Simmons
2007-02-21 22:18 ` Alex Romosan
2007-02-21 22:41 ` Richard Purdie
2007-02-21 23:17 ` Henrique de Moraes Holschuh
2007-02-22 0:12 ` Richard Purdie
2007-02-22 0:51 ` Henrique de Moraes Holschuh
2007-02-22 1:10 ` Richard Purdie
2007-02-22 2:13 ` Henrique de Moraes Holschuh
2007-02-22 1:10 ` Henrique de Moraes Holschuh
2007-02-22 1:16 ` ACPI: ibm-acpi: fix initial status of backlight device Henrique de Moraes Holschuh
2007-02-22 10:03 ` Richard Purdie
2007-02-22 14:45 ` Henrique de Moraes Holschuh
2007-02-22 18:19 ` Henrique de Moraes Holschuh
2007-02-22 10:00 ` no backlight on radeon after recent kernel "upgrade"s Richard Purdie
2007-02-22 14:56 ` Henrique de Moraes Holschuh
2007-02-22 15:19 ` Richard Purdie
2007-02-22 16:00 ` James Simmons
2007-02-22 16:34 ` Henrique de Moraes Holschuh
2007-02-22 17:08 ` Richard Purdie
2007-02-21 23:51 ` Alex Romosan
2007-02-22 1:13 ` James Simmons
2007-02-22 9:56 ` Richard Purdie
2007-02-22 14:38 ` Henrique de Moraes Holschuh
2007-02-22 4:03 ` Alex Romosan
2007-02-22 4:58 ` Alex Romosan
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=1172104471.5790.57.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=akpm@linux-foundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@onerussian.com \
--subject='Re: no backlight on radeon after recent kernel "upgrade"s' \
/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
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).