From: John Belmonte <john@neggie.net>
To: acpi-devel <acpi-devel@lists.sourceforge.net>
Cc: Charles Schwieters <charles@schwieters.org>,
Timo Hoenig <thoenig@nouse.net>,
Daniel Silverstone <dsilvers@digital-scurf.org>,
Jonathan Buzzard <jonathan@buzzard.org.uk>,
tlinux-users@linux.toshiba-dme.co.jp
Subject: [tlinux-users:07059] plans for toshiba_acpi
Date: Sun, 12 Jun 2005 10:12:49 -0400 [thread overview]
Message-ID: <42AC42E1.50801@neggie.net> (raw)
Here are my plans for enhancing the "toshiba_acpi" driver, and imploding
the "/proc/acpi/toshiba" interface.
* incorporate ACPI hotkeys patch developed by Daniel Silverstone and
used in Ubuntu Linux. Available as a run-time option, this creates a
kernel thread which polls the Toshiba firmware for hotkey events, and
passes them along to the ACPI subsystem.
* incorporate /dev/toshiba emulation patch developed by Gintautas
Miliauskas and Charles Schwieters. Available as a run-time option, this
causes toshiba_acpi to implement the "toshiba" driver's /dev/toshiba
interface (except for hotkey status). This device provides access to
the Toshiba HCI, which can be employed by userspace tools such as
"toshset" to adjust a laptop's internal Bluetooth device, display, fan,
etc. This patch has been in use since early 2004 by several users.
Regarding module auto-loading, OS's will have to resolve the ambiguity
of which driver to load (toshiba or toshiba_acpi) when /dev/toshiba is
accessed.
* add run-time option to suppress creation of /proc/acpi/toshiba. Since
the above two options cover the existing /proc/acpi/toshiba interface
and more, the proc interface can be disabled once userspace tools catch up.
Please follow up on <acpi-devel@lists.sourceforge.net>.
--John
next reply other threads:[~2005-06-12 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 14:12 John Belmonte [this message]
[not found] ` <42AC42E1.50801-wanGne27zNesTnJN9+BGXg@public.gmane.org>
2005-06-12 15:15 ` plans for toshiba_acpi Timo Hoenig
2005-06-12 19:46 ` [tlinux-users:07062] " Jonathan Buzzard
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=42AC42E1.50801@neggie.net \
--to=john@neggie.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=charles@schwieters.org \
--cc=dsilvers@digital-scurf.org \
--cc=jonathan@buzzard.org.uk \
--cc=thoenig@nouse.net \
--cc=tlinux-users@linux.toshiba-dme.co.jp \
/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