linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Ville Syrjälä" <syrjala@sci.fi>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Michel D?nzer <michel@tungstengraphics.com>,
	xorg@lists.freedesktop.org, linux-input@vger.kernel.org
Subject: Re: Warning: evdev changes - no auto-grabs anymore
Date: Fri, 15 Aug 2008 15:49:39 +0100	[thread overview]
Message-ID: <20080815144939.GV4462@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080815143921.GC16680@sci.fi>

Ville Syrjälä, le Fri 15 Aug 2008 17:39:21 +0300, a écrit :
> This also affect DirectFB and it was the original reason why I added
> EVIOCGRAB code to DirectFB's linux-input driver. Grabbing didn't cause
> problems back then but now that the input subsystem is used by
> rfkill/acpi/etc. functionalitys is lost when the devices are grabbed.

Also note that some (root-launched) daemons like brltty would like to be
notified of some given keyboard shortcut.  What they end up doing for
now is grabbing all the keyboard, and re-emiting all the keys through a
uinput.

Samuel

      reply	other threads:[~2008-08-15 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080814044337.GA11632@emu>
     [not found] ` <1218725645.907.27.camel@thor.sulgenrain.local>
     [not found]   ` <1218736209.4467.11.camel@localhost.localdomain>
     [not found]     ` <20080815002458.GA16836@emu>
     [not found]       ` <20080815065159.GA16680@sci.fi>
     [not found]         ` <20080815080247.GA17613@fooishbar.org>
2008-08-15  8:26           ` Warning: evdev changes - no auto-grabs anymore Ville Syrjälä
2008-08-15 14:10             ` Dmitry Torokhov
2008-08-15 14:31               ` Daniel Stone
2008-08-15 14:38                 ` Alan Cox
2008-08-15 14:49                 ` Dmitry Torokhov
2008-08-15 14:39               ` Ville Syrjälä
2008-08-15 14:49                 ` Samuel Thibault [this message]

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=20080815144939.GV4462@implementation.uk.xensource.com \
    --to=samuel.thibault@ens-lyon.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=michel@tungstengraphics.com \
    --cc=syrjala@sci.fi \
    --cc=xorg@lists.freedesktop.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).