-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/08/10 14:39, Ping Cheng wrote: > > Can you share how you verified the issue with us? I want to make sure > the X driver is "innocent". >
I haven't been able to get raw results from the console (I know there used to be a wacdump tool, but that doesn't seem to be a part of xf86-input-wacom). I've tried both xf86-input-wacom-0.10.6 and 0.10.8. Both worked fine up to and including 3.6.34.1, and then when I moved to 3.6.35 the problem started. Booting off an older kernel without a change to the xf86-input-wacom driver reverted the behaviour, and I was able to carry out a git bisection that way. So I've no way of telling whether the X driver's at fault, but changing the kernel back and forth definitely exhibits the problem in two versions of the X driver, which led me to believe it was the kernel change rather than a driver problem. Is there another (standard) tool for testing the kernel output without X, or should I build wacdump from the linuxwacom sources and see what it has to say? Mike 5:) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAkxz3pwACgkQu7rWomwgFXqtMQCgpMgYJVEyjZ2wGA3/TlnDClQg yoAAmwSPuwH0KCl6ZZUY4rlQvBI6cFQ8 =d3yF -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
