Oh, if I do two finger touch, I'm able to get device type to change to 2 but I also get an additional interesting message (the last line in this snippet):
[1084191.183] (II) /dev/input/event6 (10:wcmEvent): channel = 0 [1084191.183] (II) /dev/input/event6 (10:wcmEvent): c=0 i=3 t=2 s=1 x=9130 y=701 2 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=1084190800 cs=4 [1084191.183] (II) /dev/input/event6 (10:wcmFilterCoord): common->wcmRawSample = 4 [1084191.183] (II) /dev/input/event6 (10:wcmCheckSuppress): level = 2 return value = 2 [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): device type = 2 [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): Ignore non-movement relative data So perhaps touch device was set to relative mode at some point during init phase. Chris On Mon, Jan 10, 2011 at 8:45 AM, Chris Bagwell <[email protected]> wrote: > Something about that bi-sect doesn't make sense. Your pointing to a > commit that contains no code. > > I only have a few minutes with touch pad right now but tried git and > can also reproduce. > > The only thing that looked suspicious in log files is this: > > [1082669.808] (II) /dev/input/event6 (10:commonDispatchDevice): device type = > 4 > > I believe that says its detected as a cursor device? There is a case > statement for ABS_MT_SLOT that is supposed to set that value correctly > that seems not to be working now. > > Can you confirm if your using wacom-input Bamboo drivers as well? > This may be MT specific (I hope). > > Chris > > On Mon, Jan 10, 2011 at 2:22 AM, Favux ... <[email protected]> wrote: >> Hi Peter, >> >> Bisection shows it is the 12-21-10 "Merge branch 'multimonitor-purge'" >> commit. Its snapshot xf86-input-wacom-68351da breaks touch. Although >> rather than slamming to the left it jitters horizontally in place over >> about 1.5 cm. The prior commit of the same date "Bamboo tablet does >> not report device_id anymore" snapshot xf86-input-wacom-2b9eb3d still >> has working touch. >> >> Favux >> >> On Sun, Jan 9, 2011 at 11:53 PM, Peter Hutterer >> <[email protected]> wrote: >>> >>> can you run a bisect over the code to identify which commit broke it? >>> three different features got merged, multimonitor removal, the scrollring >>> fixes and chris' bamboo patches. Not sure which one caused the bug. >>> >>> Cheers, >>> Peter >>> >> >> ------------------------------------------------------------------------------ >> Gaining the trust of online customers is vital for the success of any company >> that requires sensitive data to be transmitted over the Web. Learn how to >> best implement a security strategy that keeps consumers' information secure >> and instills the confidence they need to proceed with transactions. >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Linuxwacom-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel >> > ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
