From: "Zephaniah E. Hull" <warp@aehallh.com>
To: Dmitry Torokhov <dtor@insightbb.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:12:10 -0400 [thread overview]
Message-ID: <20070612051210.GW6362@aehallh.com> (raw)
In-Reply-To: <200706120107.13655.dtor@insightbb.com>
[-- Attachment #1: Type: text/plain, Size: 2558 bytes --]
On Tue, Jun 12, 2007 at 01:07:13AM -0400, Dmitry Torokhov wrote:
> 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?
Er, to explain.
The current EVIOCGRAB does an exclusive grab that prohibits rfkill-input
and friends from working.
As it is the only way to disable the legacy input handlers,
xf86-input-evdev has been using it since we added it.
The patch is to let us cause only things that use /dev/input/event<n> to
get events, thus, a non-exclusive grab.
This basicly disables the legacy input handlers, and it's the least
invasive patch I could think of.
Going for a separate ioctl would also work, but in some ways it would
make supporting it more of a pain.
I don't care _that_ much either way, as long as we can get a way to
disable the legacy events while allowing other things to get the events
too.
Zephaniah E. Hull.
>
> 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
>
--
1024D/E65A7801 Zephaniah E. Hull <warp@aehallh.com>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
Welcome to [telco] hell. [...] You are in a maze of twisty little PVC's,
all alike. A switching engineer throws a dart at you!
-- Chris Saunderson <saundo@idx.com.au> in the scary.devil.monastery
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-12 5:12 UTC|newest]
Thread overview: 22+ 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
2007-06-12 5:12 ` Zephaniah E. Hull [this message]
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
2007-09-29 3:05 ` Ryan Lortie
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=20070612051210.GW6362@aehallh.com \
--to=warp@aehallh.com \
--cc=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@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