Chris,
I didn't get your patch yet. After revisiting your last patch, I have the
following comments:
Backward compatible is very important to third party developers since they
rely on our support. For this case, we have to support the full old
BTN_XXXTAP events (i.e. DOUBLETAP and TRIPLETAP) since there are
applications that are using those events already. Another reason we have to
provide both BTN_XXXTAPs is we need to support kernels older than 2.6.30.
Without TRIPLETAP, we can not report the second finger data.
Both TAP and MT events need to be provided in the kernel since we have no
idea which event the app is waiting for.
So, a backward compatible packet goes like this:
Standard events (in no particular order)
ABS_X
ABS_Y
...
BTN_DOUBLETAP
input_sync() <- complete the first finger
ABS_X
ABS_Y
...
BTN_TRIPLETAP
input_sync() <- complete the second finger
...
multitouch sub-packet 1:
ABS_MT_...
...
input_mt_sync() <- complete first MT sub-packet
multitouch sub-packet 2:
ABS_MT_...
...
input_mt_sync() <- complete 2nd MT sub-packet
Ping
On Wed, Mar 10, 2010 at 8:35 PM, Chris Bagwell <ch...@cnpbagwell.com> wrote:
> On Wed, Mar 10, 2010 at 11:43 AM, Ping Cheng <pingli...@gmail.com> wrote:
> > On Wed, Mar 10, 2010 at 6:44 AM, Chris Bagwell <ch...@cnpbagwell.com>
> wrote:
> >>
> >> On Tue, Mar 9, 2010 at 10:38 PM, Ping Cheng <pingli...@gmail.com>
> wrote:
> >>
> >> I'm not sure if you actively develop older kernels once you branch
> >> directories. But if you do, I think a version of my patch can be used
> >> even in non-multi-touch kernels to help keep logic aligned.
> >
> >
> > Yes, I do and I have to :). Please send your patch to me.
>
> OK, I just sent an updated patch. It is based on 0.8.5-11 to help you
> out. I used #if's to
> make old behaviour and new behaviour somewhat obvious. 0 == wraps
> code to enable old
> *TAP interface and 1 == new MT interface. The code is mutually exclusive.
>
> Chris
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
