Hi Alan,

   > So I guess the next step is to try the USB analyzer.  It will allow
   > us to see the missing data and to check that the interrupt endpoint
   > is getting polled as it should be.

Here's a screenshot comparing the broken/working traces, with NAKs hidden:

   http://dev.laptop.org/~cjb/macntouch.png

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

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.

Thanks again!

- Chris.
-- 
Chris Ball   <[EMAIL PROTECTED]>

-------------------------------------------------------------------------
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

Reply via email to