From: Arjan van de Ven <arjan@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Kristen Carlson Accardi <kristen@linux.intel.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] input: move check for same handler in input_pass_event
Date: Fri, 07 Jan 2011 11:32:33 -0800 [thread overview]
Message-ID: <4D276A51.5030102@linux.intel.com> (raw)
In-Reply-To: <20110107192938.GB28875@core.coreip.homeip.net>
On 1/7/2011 11:29 AM, Dmitry Torokhov wrote:
> On Fri, Jan 07, 2011 at 10:24:34AM -0800, Kristen Carlson Accardi wrote:
>> On Thu, 6 Jan 2011 22:04:56 -0800
>> Dmitry Torokhov<dmitry.torokhov@gmail.com> wrote:
>>
>>> On Thu, Jan 06, 2011 at 02:24:48PM -0800, Kristen Carlson Accardi wrote:
>>>> If the handler that injected an event is the same,
>>>> just skip the filter, but allow the handler->event()
>>>> routine to be called. This allows evdev to be able to
>>>> be used to loopback events.
>>> Why is it needed? Could you please give some examples?
>>>
>>> Thanks.
>>>
>> We have a customer who has a touchscreen device which sends
>> a bitmap into a gesture engine, which then interprets that
>> result and feeds it back into the kernel through a virtual
>> input driver that X is listening to.
> That really should be done though uinput.
quite possible.
but the application already exists, and works just fine in 2.6.35...
causing this to be classified as a kernel ABI regression ;-(
next prev parent reply other threads:[~2011-01-07 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 22:24 [PATCH] input: move check for same handler in input_pass_event Kristen Carlson Accardi
2011-01-06 22:29 ` Kristen Carlson Accardi
2011-01-07 6:04 ` Dmitry Torokhov
2011-01-07 18:24 ` Kristen Carlson Accardi
2011-01-07 19:29 ` Dmitry Torokhov
2011-01-07 19:32 ` Arjan van de Ven [this message]
2011-01-07 19:43 ` Dmitry Torokhov
2011-01-20 8:56 ` Dmitry Torokhov
2011-01-26 4:59 ` 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=4D276A51.5030102@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kristen@linux.intel.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).