From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Antonino A. Daplas" <adaplas@gmail.com>,
James Simmons <jsimmons@infradead.org>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
"David S. Miller" <davem@davemloft.net>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Yaroslav Halchenko <lists@onerussian.com>
Subject: Re: 2.6.21-rc2 radeon backlight
Date: Fri, 02 Mar 2007 21:34:43 -0800 [thread overview]
Message-ID: <87k5xyq498.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <1172878338.11149.198.camel@localhost.localdomain> (message from Richard Purdie on Fri, 02 Mar 2007 23:32:18 +0000)
Richard Purdie <rpurdie@rpsys.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. |
next prev parent reply other threads:[~2007-03-03 5:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ps7uutsk.fsf@sycorax.lbl.gov>
2007-03-02 2:45 ` 2.6.21-rc2 radeon backlight Andrew Morton
2007-03-02 17:24 ` Alex Romosan
2007-03-02 20:29 ` Andrew Morton
2007-03-02 20:35 ` David Miller
2007-03-02 21:01 ` Henrique de Moraes Holschuh
2007-03-02 21:22 ` Alex Romosan
2007-03-02 21:40 ` David Miller
2007-03-02 21:41 ` James Simmons
2007-03-02 21:58 ` Andrew Morton
2007-03-02 23:40 ` [Linux-fbdev-devel] " Richard Purdie
2007-03-03 16:23 ` James Simmons
2007-03-02 23:32 ` Richard Purdie
2007-03-03 5:34 ` Alex Romosan [this message]
2007-03-03 16:06 ` James Simmons
2007-03-03 16:35 ` Richard Purdie
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=87k5xyq498.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hmh@hmh.eng.br \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@onerussian.com \
--cc=rpurdie@rpsys.net \
/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;
as well as URLs for NNTP newsgroup(s).