Re: Re: [patch 1/1] thinkpad fn+fx key driver

[Timo Hoenig <thoenig-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]

Hi,

On Thu, 2004-09-23 at 13:24 +0200, Vojtech Pavlik wrote:
> On Thu, Sep 23, 2004 at 01:16:57AM -0400, Brown, Len wrote:

[...]

> There are several ways to make both the keyboard and ACPI keys work as
> intended:
> 
> 1) Extend acpid to listen on all /dev/input/event keyboard devices and
>    call scripts when the keys are pressed. No change to the kernel.
> 
> 2) Change ACPI to use the Input API, and add possibility to map ACPI
>    events in the keymap. Then have acpid listen to those.
> 
> 3) Change ACPI to use the Input API and use the power.ko module for
>    mapping the keys to system state change actions.
> 
> 4) Change ACPI to use the Input API and have a daemon that handles
>    all extra keys, including sound volume and application keys, possibly
>    using D-bus to send the events to the desktop environment.
> 
> 5) Change power.ko to just generate ACPI events for the keys. Handle
>    the events via acpid.
> 
> I probably prefer 4), although all make sense. I think 3) is only useful
> for embedded systems, because it's not configurable enough. 2) would
> probably not work when in X, because it relies on the console subsystem.

Since I am working on a project (Input Abstraction Layer) which is
exactly what Pavlik mentioned with 4) I wanted to raise my voice. It is
a daemon which can easily be enhanced by modules which are dynamically
loaded. There are going to be three different module types: Input,
output and in/output modules.

Input modules simply gather events and send them via D-Bus to clients
(for example: module for normal ACPI events).

Output modules do not gather data but can receive messages from clients
and react on these messages (for example: module for the new sony_acpi
driver).

In- & Output modules do both (for example: module for the toshiba_acpi
driver).

I'm blogging about the development on http://thesis.nouse.net. Expect a
first version within the next four weeks.

   Timo

..............................................................
Timo Hönig <thoenig at nouse dot net>
..................................................:: gpg ::...
Fingerprint: 0998 0ACA A1D2 2612 4D96 DD8B E03F 084B B305 4066

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]