hi : thanks U :-) 2011/3/25 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > On Fri, 25 Mar 2011, loody wrote: > >> I use usb mon to capture the iso and interrupt log. >> But I cannot quite understand the message mean. >> >> 87230124 328084000 S Ii:1:007:1 -150:1 1025 < >> 87230124 328084000 C Ii:1:007:1 0:1 7 = 0e05010a fc0001 >> >> 8719dd00 530320000 S Zo:2:003:1 -150:1:0 8 -18:0:176 -18:176:176 >> -18:352:176 -18:528:176 -18:704:176 1408 D >> 8719dd00 530336000 C Zo:2:003:1 0:1:20:0 8 0:0:176 0:176:176 0:352:176 >> 0:528:176 0:704:176 1408 > >> >> what does the "-150:1" and " -150:1:0 8 -18:0:176 -18:176:176" mean? >> I guess that maybe status and interval, where I can find the >> definition table in driver to check it? > > The -150 and -18 values are status codes. The :1 and :1: values are > urb->interval, the :0 is urb->start_frame, and the 8 is > urb->number_of_packets. The :0: and :176: values are > iso_frame_desc[n].offset (where n is 0 and 1 respectively), and the > :176 values are iso_frame_desc[n].length. > > The status codes are listed in arch/.../include/asm/errno.h (fill in > the ... with whatever architecture you are using) and defined in > Documentation/usb/error-codes.txt. Your letter is coming when I want to say I found where it is, mon_text.c, and it will print out the text output by different kind node, right? appreciate your help, miloody -- 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
