Message-ID: <477B5FD8.5070503@msgid.tls.msk.ru>
Date: Wed, 02 Jan 2008 12:56:40 +0300
From: Michael Tokarev <mjt@tls.msk.ru>
Organization: Telecom Service, JSC
User-Agent: Icedove 1.5.0.14pre (X11/20071018)
MIME-Version: 1.0
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: acpi/apm events as inputs: how to handle?
OpenPGP: id=4F9CF57E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1430
Lines: 40

(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?

Thanks!

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/