public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Corentin CHARY <corentincj@iksaif.net>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, acpi4asus-user@lists.sourceforge.net
Subject: [patch 0/7] New misc/asus-laptop.c driver
Date: Thu, 25 Jan 2007 12:54:33 +0100	[thread overview]
Message-ID: <200701251254.34491.corentincj@iksaif.net> (raw)

Hi,
I've done a lot of work on asus_acpi, see :

diff asus_acpi.c asus-laptop.c -u | diffstat
 asus-laptop.c | 1663 
++++++++++++++++++++++++----------------------------------
 1 file changed, 711 insertions(+), 952 deletions(-)

So because the new driver work in a very different way, and have a new 
interface (no more /proc/acpi/asus/), I think it's time for 
misc/asus-laptop.c, but we should also keep asus_acpi.c for sometime.

In asus_acpi, we had to add all models by hand, and the list was growing very 
fast... The new detection system is inspired by ibm-acpi (we search well 
known acpi method, and if we found one then the feature is available).

Now leds are handled by /sys/class/led/asus:*/ , backlight 
with /sys/class/backlight/asus-laptop/ .
asus-laptop is now a platform driver, so files like wlan, bluetooth, 
ls_switch, ls_level, info, etc .. are now 
in /sys/devices/platform/asus-laptop/ .

These patch are designed to apply to  acpi-test-20060707-2.6.20-rc4, but as 
it's a new driver, it's easy to apply against other trees.

-- 
CHARY 'Iksaif' Corentin
http://xf.iksaif.net

             reply	other threads:[~2007-01-25 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 11:54 Corentin CHARY [this message]
2007-01-26  7:51 ` [patch 0/7] New misc/asus-laptop.c driver Len Brown
2007-01-26 13:04   ` Corentin CHARY
2007-01-30  7:53     ` Len Brown
2007-01-30  8:28       ` Corentin CHARY

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=200701251254.34491.corentincj@iksaif.net \
    --to=corentincj@iksaif.net \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.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