W dniu 9 stycznia 2012 23:25 użytkownik Peter Stuge <peter@xxxxxxxx> napisał: > Rafał Miłecki wrote: >> I've been using "usbmon" to dump traffic. > > The tool at http://people.redhat.com/zaitcev/linux/usbmon-6.tar.gz > and not simply cat on the usbmon files in debugfs I hope. > > debugfs only shows the first bytes of long transfers, but the API > used by the usbmon-6 tool shows complete traffic. I think I start to understand. The number before "<" or "=" or ">" is amount of bytes. For example: ea700b40 493839847 S Bi:2:003:6 -115 8 < We just asked for 8 bytes ea700b40 493840818 C Bi:2:003:6 0 8 = 00060456 00000000 Here we received the 8 bytes. f3dad540 493840838 S Bi:2:003:6 -115 13 < We asked for 13 bytes. f3dad540 493840923 C Bi:2:003:6 0 13 = 55534253 0a1a0000 00000000 00 The requested 13 bytes. Now some bigger amount: eb48d640 504977573 S Ci:2:010:0 s 80 06 0200 0000 0027 39 < Asking for 39bytes? eb48d640 504977936 C Ci:2:010:0 0 39 = 09022700 010100a0 64090400 0003ff02 ff000705 81031000 04070582 02000200 Only 32bytes received? Is this the issue you meant? Am I correctly parsing that dumps? I've quickly tried usbmon userspace tool, but not much more luck with it. Example from this tool: f2c19e40 6.317817 S Ci:2:013:0 s 80 06 0200 0000 0027 39 < f2c19e40 6.318305 C Ci:2:013:0 0 39 = 09022700 010100a0 64090400 0003ff02 ff000705 81031000 04070582 02000200 . . ' . . . . . d . . . . . . . . . . . . . . . . . . . . . . . Maybe it requires some switch or sth... unfortunately it's not documented at all ;/ -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
