Hello, I'm trying to understand the usbsnoop log in attachment.
The usb device is an isdn ta.
We've 3 endpoints (2 int in and 1 isoc out).
After selecting configuration, the device driver submits 2 interrupt urbs (one for each int endpoint) that remain in -EINPROGRESS.
Then it submits an ASAP isochronous urb that resubmits itsself when it's completed.
Usbsnoop log shows me the buffer content only for the first urb (a sequence of \x00, \x01, \x02 and \x03) but it's the only out endpoint I have so I think every command should go through it.
Am I wrong?
Sending the simplest command (opening a isdn utility that makes the driver led switched on), the first interrupt urb comes back (after "URB 521 going down") and then it's resubmitted. Where did I tell the device "ok now switch me on the driver led" ?
I tried a lot of usb sniffer (sniff1.3, sniff1.8 by papilloit, usbsnoopy at sourceforge, wdmsniffer utility by Compuware) but I can't understand what happens on the bus.
Any idea? Thanks magneto
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
