Re: [PATCH] input: move check for same handler in input_pass_event

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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.

Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux