From: Marcel Holtmann <marcel@holtmann.org>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org
Subject: Global /dev/input/events device
Date: Fri, 05 Jun 2009 15:54:39 +0200 [thread overview]
Message-ID: <1244210079.23850.32.camel@localhost.localdomain> (raw)
Hi Dmitry,
so I am working on creating a replacement for the kernel RFKILL input
support with a proper daemon in userspace that allows us to implement
proper policy support for RFKILL soft switch event buttons.
What I am missing is a /dev/input/events device (similar to the mice
device) that combines all events into one to make it easier for
application if they really don't care which actual physical or virtual
device created that event. Is it possible that we create something like
this?
Regards
Marcel
next reply other threads:[~2009-06-05 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:54 Marcel Holtmann [this message]
2009-06-05 15:03 ` Global /dev/input/events device Dmitry Torokhov
2009-06-05 15:10 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244210079.23850.32.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).