From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-input@vger.kernel.org
Subject: Re: Global /dev/input/events device
Date: Fri, 5 Jun 2009 08:03:08 -0700 [thread overview]
Message-ID: <20090605150307.GA14901@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <1244210079.23850.32.camel@localhost.localdomain>
Hi Marcel,
On Fri, Jun 05, 2009 at 03:54:39PM +0200, Marcel Holtmann wrote:
> 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?
>
I really don't think that creating such device is in out best interest.
We just went through this with /dev/input/mice and X using legacy
keybpard driver. Inevitably people start trying to remove certain
devices from the multiplexed stream coming up with crazy and fragile
exclusion schemes that only bring more problems in the long run.
Just have your daemon listen to hotplug/dbus events and select() from
all devices you are interested in. Then it will be easier later on to
ignore some devices users feel should not be taken into account.
--
Dmitry
next prev parent reply other threads:[~2009-06-05 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:54 Global /dev/input/events device Marcel Holtmann
2009-06-05 15:03 ` Dmitry Torokhov [this message]
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=20090605150307.GA14901@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=marcel@holtmann.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).