From: Dmitry Torokhov <dtor@insightbb.com>
To: "Zephaniah E. Hull" <warp@aehallh.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Support for a less exclusive grab.
Date: Tue, 12 Jun 2007 01:07:13 -0400 [thread overview]
Message-ID: <200706120107.13655.dtor@insightbb.com> (raw)
In-Reply-To: <20070609084800.GR6362@aehallh.com>
Hi Zephaniah,
On Saturday 09 June 2007 04:48, Zephaniah E. Hull wrote:
> EVIOCGRAB is nice and very useful, however over time I've gotten
> multiple requests to make it possible for applications to get events
> straight from the event device while xf86-input-evdev is getting events
> from the same device.
>
> Here is the least invasive patch I could think of, it changes the
> behavior of EVIOCGRAB in some cases, specificly behavior is identical if
> the argument is 0 or 1, however if the argument is true and != 1, then
> it does a 'non exclusive grab', a better name might be handy.
>
> What this does is allow the events to go to everything that's using
> evdev to get events, but grabs it from anything else. About as close to
> what people want as I can get, and fairly non-invasive.
Unfortunately this also robs non-legacy input handlers (such as
rfkill-input) of input events. Does xf86-input-evdev really needs to
grab devices exclusively? I guess we can't abandon the standard
keyboard driver until X supports hotplugging. How close is it to
support devices coming and going?
If we can't remain as is until X hotplug is ready then I'd rather had
a separate ioctl that disables legacy input handlers (keyboard, mousedev)
for a given input device.
--
Dmitry
next prev parent reply other threads:[~2007-06-12 5:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 8:48 [PATCH] Input: Support for a less exclusive grab Zephaniah E. Hull
2007-06-12 5:07 ` Dmitry Torokhov [this message]
2007-06-12 5:12 ` Zephaniah E. Hull
2007-06-12 5:19 ` Dmitry Torokhov
2007-06-12 5:23 ` Zephaniah E. Hull
2007-06-12 5:35 ` Dmitry Torokhov
2007-06-12 5:40 ` Zephaniah E. Hull
2007-07-02 15:20 ` Vojtech Pavlik
2007-07-03 16:45 ` Zephaniah E. Hull
2007-07-03 22:15 ` Vojtech Pavlik
[not found] ` <1191035147.7025.28.camel@moonpix.desrt.ca>
2007-10-23 13:21 ` Dmitry Torokhov
2007-10-23 15:57 ` Ryan Lortie
2007-10-23 18:10 ` Dmitry Torokhov
2007-10-24 1:58 ` Ryan Lortie
2007-10-24 3:33 ` Dmitry Torokhov
2007-10-24 15:35 ` Zephaniah E. Hull
2007-10-25 5:37 ` Ryan Lortie
2007-10-26 16:44 ` Zephaniah E. Hull
2007-10-26 17:16 ` Ryan Lortie
2007-10-26 17:58 ` Zephaniah E. Hull
2007-10-26 17:29 ` Dmitry Torokhov
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=200706120107.13655.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=warp@aehallh.com \
/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).