From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: rpurdie@rpsys.net, romosan@sycorax.lbl.gov,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc2 radeon backlight
Date: Fri, 02 Mar 2007 12:35:14 -0800 (PST) [thread overview]
Message-ID: <20070302.123514.35465791.davem@davemloft.net> (raw)
In-Reply-To: <20070302122920.a2967ebf.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Fri, 2 Mar 2007 12:29:20 -0800
> On Fri, 02 Mar 2007 09:24:03 -0800
> Alex Romosan <romosan@sycorax.lbl.gov> wrote:
>
> > Andrew Morton <akpm@linux-foundation.org> writes:
> >
> > > On Wed, 28 Feb 2007 08:32:43 -0800
> > > Alex Romosan <romosan@sycorax.lbl.gov> wrote:
> > >
> > >> the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
> > >> on if i have the radeon backlight enabled. without it, i guess it's
> > >> the ibm acpi modules that controls the backlight and it seems to work
> > >> fine.
> > >>
> > >
> > > Unclear. Are you saying that the backlight comes on OK if you use
> > > the IBM acpi module?
> >
> > yes, if i disable the radeon backlight and use the ibm acpi module,
> > than the backlight works. if i enable the radeon backlight, the screen
> > stays dark and i can't turn it on (i tried using radeontool to control
> > it but nothing happened).
>
> Richard, is this actually a bug, or is it a config error or something like that?
>
> And should we track it as a post-2.6.20 regression?
Why don't we compromise for 2.6.21 by marking the Radeon backlight
stuff EXPERIMENTAL until the cases where IBM ACPI works and the
Radeon backlight stuff does not are worked out?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-02 20:35 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 [this message]
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
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=20070302.123514.35465791.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
--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).