From: Matt Domsch <Matt_Domsch@dell.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Alessandro Guido <alessandro.guido@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, jengelh@linux01.gwdg.de, gelma@gelma.net,
ismail@pardus.org.tr
Subject: Re: [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver
Date: Fri, 6 Oct 2006 16:17:51 -0500 [thread overview]
Message-ID: <20061006211751.GA31887@lists.us.dell.com> (raw)
In-Reply-To: <20061005103657.GA4474@ucw.cz>
On Thu, Oct 05, 2006 at 10:36:57AM +0000, Pavel Machek wrote:
> Hi!
>
> > > I assume that cute userspace applications for controlling backlight
> > > brightness via the generic backlight driver either exist or are in
> > > progress? What is the status of that?
> >
> > For Dell laptops, the dellLcdBrightness app is included in the
> > libsmbios-bin package (http://linux.dell.com/libsmbios/main/ and
> > http://linux.dell.com/libsmbios/main/yum.html for the yum repo). It's
> > entirely userspace.
>
> Please move it into the kernel where it belongs, and use lcd
> brightness subsystem like everyone else.
We've been through this before.
http://marc.theaimsgroup.com/?l=linux-kernel&m=114067198323596&w=2
In addition, the SMI call used to change the backlight level *may*
require (if configured by the sysadmin in BIOS), a password be
entered.
This begs for a common userspace app that can grok libsmbios and
kernel interfaces both, and use the appropriate method on each, rather
than just putting it all in the kernel.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2006-10-06 21:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 17:08 [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver Alessandro Guido
2006-09-30 17:14 ` Alessandro Guido
2006-09-30 17:31 ` Jan Engelhardt
2006-10-02 0:19 ` Andrew Morton
2006-10-02 0:39 ` Matt Domsch
2006-10-02 0:48 ` Matt Domsch
2006-10-05 10:36 ` Pavel Machek
2006-10-06 21:17 ` Matt Domsch [this message]
2006-10-06 22:44 ` Pavel Machek
2006-10-10 14:32 ` Yu Luming
2006-10-10 14:47 ` Richard Hughes
2006-10-10 16:10 ` Matt Domsch
2006-10-11 16:28 ` Yu Luming
2006-10-16 17:45 ` Yu Luming
2006-10-25 7:07 ` Pavel Machek
2006-10-27 17:24 ` Luming Yu
2006-10-29 17:50 ` Pavel Machek
2006-10-30 15:49 ` Luming Yu
2006-10-10 21:26 ` Matthew Garrett
2006-10-11 3:02 ` Matt Domsch
2006-10-11 3:16 ` Matthew Garrett
2006-10-11 16:37 ` Yu Luming
2006-10-11 6:59 ` Arjan van de Ven
2006-10-11 7:04 ` Matthew Garrett
2006-10-11 8:04 ` Ismail Donmez
2006-10-11 8:12 ` Matthew Garrett
2006-10-11 16:31 ` Yu Luming
2006-10-11 16:45 ` Ismail Donmez
2006-10-02 10:29 ` Holger Macht
2006-10-02 11:25 ` Alessandro Guido
2006-10-10 15:17 ` Yu Luming
2006-10-10 15:22 ` Richard Hughes
2006-10-10 21:23 ` Matthew Garrett
2006-10-11 3:20 ` Dmitry Torokhov
2006-10-11 16:48 ` Yu Luming
2006-10-11 19:08 ` Dmitry Torokhov
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=20061006211751.GA31887@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alessandro.guido@gmail.com \
--cc=gelma@gelma.net \
--cc=ismail@pardus.org.tr \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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