[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k5xyq498.fsf@sycorax.lbl.gov>
Date: Fri, 02 Mar 2007 21:34:43 -0800
From: Alex Romosan <romosan@...orax.lbl.gov>
To: Richard Purdie <rpurdie@...ys.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"Antonino A. Daplas" <adaplas@...il.com>,
James Simmons <jsimmons@...radead.org>,
linux-kernel@...r.kernel.org,
linux-fbdev-devel@...ts.sourceforge.net,
"David S. Miller" <davem@...emloft.net>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Yaroslav Halchenko <lists@...russian.com>
Subject: Re: 2.6.21-rc2 radeon backlight
Richard Purdie <rpurdie@...ys.net> writes:
> I propose the following patch (I was previously waiting on James for
> this). It avoids backing out the problematic Kconfig changes but
> means a user has to explicitly enable the backlight via a kernel or
> module parameter.
>
> Can people with backlight problems try enabling them in Kconfig but
> applying the following patch? Hopefully I have you all cc'd.
>
> If it works I will add it to the other fix I have queued and pass to
> Linus via the backlight tree. If it doesn't, I will revert the
> problematic Kconfig changes for the next -rc.
with the patch applied i can boot into 2.6.21-rc2 and have a working
backlight when i enable radeon backlight support. so i guess the patch
successfully disables the new radeon backlight stuff on my thinkpad
and therefore it does what it says it does.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists