HAL and INPUT

[Arnaud Quette]

[adding the LIRC list]

2007/7/3, Richard Hughes <hughsient at gmail.com>:
> Guys,
>
> What are we doing with HAL and INPUT? Currently HAL exposes buttons such
> as LID with state and other buttons such as POWER without state.
>
> With the new INPUT world-order, we will have several event devices that
> can emit devices of different types.
>
> If we are planning to support the new buttons produced by the likes of
> thinkpad_acpi (where we can detect what buttons are attached, but can
> remap them on the fly) then we need to make sane the HAL policy and keys
> for this.
>
> So we have:
>
> * switches that have state like lid
> * buttons that give out events
> * keyboards that have to be remapped (kernel drivers included)
>
> I think we need to decide what we need to do, as the current code in HAL
> is hacky and really confusing as we are merging devices to computer and
> creating other devices with different properties.
>
> So I think, ideally we need to do:
>
> * hardware remaping of keys using the keymap addon
> * for each input device:
>  - create a new individual hal device for any 'interesting' buttons and
> launch an addon monitoring the event file.
>  - and buttons that have state then merge in the extra properties
>
> Or we can rip out all the input parts from HAL (but keep keymap) and
> just reply on querying XOrg for buttons and state.
>
> Comments please,

as a side note, I'm also interested in this, since I'm considering the
inclusion of Remote Controls support through LIRC. Any input welcome.

Arnaud
-- 
Free Software Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team