HAL doesn't work with grabbed or uinput created devices

[Richard Hughes]

On Tue, 2007-01-16 at 17:54 +0000, Johannes Berg wrote:
> 
> hal will, for example, listen to the brightness buttons and send
> button
> events across the system bus. When inputd comes in, that (and along
> with
> it g-p-m) stops working.
> 
> Additionally, we currently have a FN mode flag inside the kernel which
> could be moved to inputd, which means that inputd output needs to be
> handled by hal.

Why move stuff like this out of the kernel?

Why not just send the key presses as input events, which as I understand
it, is exactly what the ACPI layer in the kernel is converting to. The
only reason the ibm and toshiba addons are in HAL is so the buttons work
now, and were added before the kernel guys were happy depending on
INPUT.

In my opinion, the kernel shouldn't do random things that need
abstracting by HAL, the kernel should do one sane thing, which is use
the input layer for multimedia buttons just like any other buttons.

What's the use case for using inputd?

Richard.