On Mon, 30 Jul 2007, Chris Ball wrote: > Here's a screenshot comparing the broken/working traces, with NAKs hidden: > > http://dev.laptop.org/~cjb/macntouch.png
Too low-resolution to see anything. But it doesn't matter since the log file has most of the info. > Both traces are from plugging in and hitting "a" three times. Here's a > text file of the log from the failing case -- it shows that IN-NAKs > are happening regularly after the final GetDescriptor (which you can > get to in the file by searching for "9.534"): > > http://dev.laptop.org/~cjb/macntouch.log Yes, I see them. It even shows the IN-NAKs for interrupt endpoints 2 and 4. > I checked to see whether /proc/interrupts increases with each keypress; > it increases twice per keypress in the working case and not at all in > the failing one. > > Any further ideas? I can't imagine what's wrong with my hardware. It > works on other PPC laptops running Linux, though I haven't found another > of the same model of Powerbook to test with. The only other variables I can think of are timing, which shouldn't matter much, and voltage, which also shouldn't matter as long as the device works at all. So I don't know. Obviously the keyboard is malfunctioning, but we may never find out exactly why. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
