On Tue, Feb 9, 2010 at 8:05 PM, Chris Bagwell <[email protected]> wrote: > Can someone double check following logic issue? There happens to be > two places in log files below were first fingers Y values are same as > second fingers Y values on kernel side. In those cases, it looks like > this same value is not sent to X driver. > > While fingers were in proximity, it meant channel 1 kept its older Y > value. When first coming in to proximity, it meant Y was at a zero > value (from a memset() it seems) and some events got discarded because > less then 3 events were received.
If everything works properly (all data are different), channel 0 would keep finger one data, channel 1 would keep finger 2 data, and channel 2 would kees pad data, if the tablet has a pad. If there are duplicated data, only the first one will be received by X driver as we discussed before. In the case you described above, I think we need to copy the first finger data to channel 1 (i.e., duplicate channel 1 with channel 0's data) to avoid zeros. Please test this solution to see how it works. Thank you, Ping ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
