HAL FDI matched Buttons

[Richard Hughes]

On Mon, 2005-11-28 at 16:05 +0100, Matthias Grimm wrote:
> On Sun, 27 Nov 2005 23:33:30 +0000
> Richard Hughes <hughsient at gmail.com> wrote:
> 
> > Using the fdi on my system, pressing Fn-F4 triggers a KEY_BRIGHTNESSUP X
> > input which can be read by GNOME Keyboard Shortcuts, and it also send a
> > ButtonPressed condition that can be monitored by anything with a DBUS
> > interface.
> 
> Sounds good so far.

Cool.

> > This method would also work for laptop models that generate acpi events
> > rather than having to poll a certain file (like Toshibas do).
> 
> Who does the file polling then? I saw you fdi file but don't understand
> who does the work? IALd has a module system (I would call the user
> space device driver) for this so that I can simply read /proc/acpi for
> buttons in one driver and poll /dev/pmu for PMU interrupts in another.
> HAL doesn't have such a system of "user space device drivers" yet.

The specific addon for toshiba laptops. Toshiba acpi extensions are
really messed up with the button handling, only presenting a pollable
interface, i.e. with no interrupts. The rest of the acpi laptops out
there should generate acpi events for extra buttons, which we can
trivially catch in the existing acpi addon.

Richard.