From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, romosan@sycorax.lbl.gov,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, rpurdie@rpsys.net
Subject: Re: 2.6.21-rc2 radeon backlight
Date: Fri, 2 Mar 2007 18:01:57 -0300 [thread overview]
Message-ID: <20070302210157.GA11786@khazad-dum.debian.net> (raw)
In-Reply-To: <20070302.123514.35465791.davem@davemloft.net>
On Fri, 02 Mar 2007, David Miller wrote:
> 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?
What ibm-acpi backlight control does is *very* different from what the
radeon backlight control does.
ibm-acpi talks to the ThinkPad EC to change the brightness of the backlight,
it has *NO* on/off support. Radeon talks to the video chipset to turn the
LVDS output on/off (or something to that effect), and thus to turn the
backlight on/off.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-03-02 21:01 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 [this message]
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=20070302210157.GA11786@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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).