All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zephaniah E. Hull" <warp@aehallh.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Support for a less exclusive grab.
Date: Tue, 3 Jul 2007 12:45:55 -0400	[thread overview]
Message-ID: <20070703164555.GA20370@aehallh.com> (raw)
In-Reply-To: <20070702152044.GA24665@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

On Mon, Jul 02, 2007 at 05:20:44PM +0200, Vojtech Pavlik wrote:
> On Tue, Jun 12, 2007 at 01:40:31AM -0400, Zephaniah E. Hull wrote:
> > On Tue, Jun 12, 2007 at 01:35:05AM -0400, Dmitry Torokhov wrote:
> > > On Tuesday 12 June 2007 01:23, Zephaniah E. Hull wrote:
> > > > On Tue, Jun 12, 2007 at 01:19:59AM -0400, Dmitry Torokhov wrote:
> > > > > 
> > > > > Like I said I would love if xf86-input-evdev did not grab the
> > > > > device at all.
> > > > 
> > > > We have to disable the legacy input handlers somehow, not doing so
> > > > simply isn't an option.
> > > 
> > > I do not follow. If user's xorg.conf does not use /dev/input/mice and
> > > does not use "kbd" driver then grabbing is not required, is it? Now,
> > > as far as I understand, lack of hotplug support in X is the main
> > > obstacle for removing "mouse" and "kbd" drivers, correct?
> > 
> > Sadly, not quite.
> > 
> > The problem is that if the user is not using the mouse and kbd drivers
> > at all, but is instead using xf86-input-evdev, and no grabbing is done,
> > then all key presses end up going to the console.
> 
> X still switches to its own VT, so those keys go to the X server via the
> console, and GPM also knows about console switching ...
> 
> That is a sane way how to prevent the regular console from getting
> keypresses/mouse movements.

Not really, what happens when the user presses alt-F1?  A way to tell
the kernel that events from a given input device should not go to the
console has been needed since the very first time an X driver allowed
keyboard events from /dev/input/event<n>, and that still has not
changed.

We just want a more flexible approach then what we are already using[0].

I'll see about writing something up when I get back to my computers[1]
and have things set back up[2].

Zephaniah E. Hull.

0: EVIOCGRAB.
1: The night of the 10th.
2: It could be a few days after I get back.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-03 16:45 UTC|newest]

Thread overview: 23+ 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
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 [this message]
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
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=20070703164555.GA20370@aehallh.com \
    --to=warp@aehallh.com \
    --cc=dtor@insightbb.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.