On Wed 2008-01-02 12:56:40, Michael Tokarev wrote:
> (Not so) recently, ACPI events started appearing as
> key press events over linux input subsystem. The
> question regarding this is simple: how it's supposed
> to be handled?
>
> First of all, I don't know any software so far that
> can handle input layer in userspace when not running
> X. In X, it's usually done using window manager
> setup or with special application (like, volume
> up/down keys etc). But without X, there's no such
> application, as far as I can see.
>
> It's easy to write one, but there may be.. issues
> with finding which input device to use.
>
> Now, linux already have hotplug subsystem, using
> /sbin/hotplug helper (or whatever it points to,
> or using netlink). ACPI key events are rare.
>
> What I'm thinking about is: why ACPI events are
> routed over input subsystem, instead of hotplug
> subsystem? With input, there's a need for a
> special daemon/application listening on the
> specific "keyboard" device, while with hotplug
> subsystem, it's already here - linux (by default
> anyway, if not running udev etc), kernel fires
> up a script when an event occurs. I don't see
> how this special application/daemon is different
> from ol'good acpid.
>
> Or.. maybe I missed something?
No, you are not missing anything. Yes, we could use /sbin/hotplug, but
it would be an ugly hack. So better write that daemon, or teach udevd
to read from input...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
