Sorry, I ment to reply to all. Forwarding what I sent to Chris. ---------- Forwarded message ---------- From: Bryan Hundven <bryanhund...@gmail.com> Date: Sat, Mar 6, 2010 at 10:55 PM Subject: Re: [Linuxwacom-devel] [PATCH 5/5] Remove ISDV4-specific code from wcmReadPacket(). To: Chris Bagwell <ch...@cnpbagwell.com>
On Sat, Mar 6, 2010 at 11:27 AM, Chris Bagwell <ch...@cnpbagwell.com> wrote: > Bryan, > > Have you seen this bug report about needing to upgrade your firmware? > Are you running latest firmware? > > http://sourceforge.net/tracker/index.php?func=detail&aid=1659939&group_id=69596&atid=525124 > > If this is what your seeing then the changes I'm suggesting will just > increase stability but will not 100% fix the issue. Its one thing if > hardware is randomly putting zeros at end of packet but the examples > in that bug report is showing it randomly putting zero's in random > locations inside packet. That can't really be handled very well by > driver. $ sudo dmidecode -s bios-version 7SET38WW (1.24 ) I have not seen this bug, but this is interesting. If you look at the change log, 1.12 does not exist. http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-68006 > I'm trying to guess a way for you to get similar hex dump of your > touchscreen output. Perhaps the following will work when your not > running X (or at least not with wacom driver): > > sudo cat /dev/ttyS0 | od -x > > Then do some basic pen drawing that you know has issues. > > Break the returned values up so that each line starts with 0xa1, 0xa0, > 0x91, or 0x90. As best I know, the 0xa? values should always have 8 > bytes following it (9 total) and the 0x9? values should have 4 bytes > (total of 5). If you see more values between packet headers then your > most likely seeing a firmware type issue. > > FYI: Packets starting with 0x9? are finger touchs and the lower 0/1 > means press/release of touch. 0xa? means pen/eraser with 0/1 meaning > press/release. Something else in packet tells further if its pen vs. > eraser. od, xxd, and hexdump... I've had issues using some of my usual friends (awk, sed, cut) to parse their output. Gimmie some time, and I'll get you some output that is useful. Interesting... I downloaded the latest 0.8.5-11, and built wacdump. Start wacdump: wacdump -c serial -f tpc /dev/ttyS0 After it starts up, initially says: WARN: Bad high bit, discarding 2 bytes When I try to draw with the pen it says: WARN: resetting tablet due to errors Then goes to: ERROR: LOBIT ERROR Which go back to the first warning after <ctrl>+c out of wacdump and starting it back up again. I also note that wacdump says ROM=0.0-0 and TOOLTYPE=none... odd. I tried setting the "Wacom Debug Levels", but maybe my xinput is older? $ xinput --set-prop "stylus" "Wacom Debug Levels" 10 10 property Wacom Debug Levels doesn't exist, you need to specify its type and format from xinput --help: xinput set-prop <device> [--type=atom|float|int] [--format=8|16|32] <property> <val> [<val> ...] Do you know the type and format? > 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
