From: Chris Larson <kergoth@handhelds.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Nicolas Pitre <nico@cam.org>,
Frank Becker <fbecker@intrinsyc.com>,
Chris Larson <kergoth@handhelds.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: backlight/frontlight
Date: Fri, 20 Dec 2002 12:33:59 -0700 [thread overview]
Message-ID: <20021220193359.GB4550@rikers.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0212201813390.6471-100000@phoenix.infradead.org>
* James Simmons (jsimmons@infradead.org) wrote:
>
> Oh. Could someone list all the approaches people toke to solve this
> problem. I like to find a solution that covers as many cases as possible.
James,
As far as I know, the two that seem worth looking at, at the moment,
are Russ Dill's implementation, which was posted to the LAK list in this
thread, and Nicolas' implementation in the -pxa patches.
There are obviously others out there, but said other implementations are
individual hacks for certain machine types, and aren't generally useful.
--
Chris Larson
kergoth at handhelds dot org
OpenZaurus Project Maintainer - http://openzaurus.org/
-------------------------------------------------------------------
Subscription options: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ/Etiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php
next prev parent reply other threads:[~2002-12-20 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021219193645.B25149@flint.arm.linux.org.uk>
2002-12-20 18:13 ` backlight/frontlight James Simmons
2002-12-20 18:14 ` backlight/frontlight James Simmons
2002-12-20 19:33 ` Chris Larson [this message]
2002-12-20 21:20 ` backlight/frontlight Frank Becker
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=20021220193359.GB4550@rikers.org \
--to=kergoth@handhelds.org \
--cc=fbecker@intrinsyc.com \
--cc=jsimmons@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux@arm.linux.org.uk \
--cc=nico@cam.org \
/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).