Oliver: I tried the standard windows USB CDC ACM driver and a standard inf file on Windows XP and I found that it also hangs. So I'm going to focus on what transactions are different between the mfgr's driver and standard Windows USB snoop logs are somewhat different in some cases in setup and also in Interrupt transfers. I am going to try the mfgr's inf file with the appropriate changes to use the standard Windows CDC ACM driver so that I can eliminate the inf file differences. Are you aware of any scripts that can completely parse a CDC-ACM dump. It's been quite painful to keep going back to the USB specification to decode the setup messages etc. I found a non-free tool called USBlyzer which has a free 30 day eval and I will try it Regards Ashok On Tue, Jun 5, 2012 at 4:11 AM, Oliver Neukum <oliver@xxxxxxxxxx> wrote: > Am Mittwoch, 30. Mai 2012, 19:58:52 schrieb Ashok Rao: >> 7. I am speculating that the barrage of packets to the IN endpoint >> caused the Satphone to freeze somehow and not accept the packets on >> the right OUT endpoint. I have read your earlier response and will >> try lsusb in this state and see if it responds. > > This can be tested. In cdc-acm.h please reduce the number of buffers > > #define ACM_NW 16 > #define ACM_NR 16 > > You can go down to 2 (1 might not work) > > Regards > Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
