Mahlzeit
On Mon, Aug 18, 2003 at 03:38:01PM -0400, Alan Stern wrote:
> Without knowing your situation it's hard to say anything definite. But
> probably what's wrong is that your device isn't sending any data, and
> that's why you're not receiving any. You haven't said what Interrupt
> response your bus analyzer shows, but it might simply be NAKs. As for why
> your device won't send the data -- I don't know.
My USB analyzer log shows on a faulty run:
1271: OUT (>> 0xe1) ADDR (0x3) EP (0x2)
1272: DATA0 (>> 0xc3) DATA(0 04 00 e2 c1 00 23)
1273: ACK (<< 0xd2)
1287: OUT (>> 0xe1) ADDR (0x3) EP (0x2)
1288: DATA1 (>> 0x4b) DATA(0 04 00 e2 c0 00 22)
1289: ACK (<< 0xd2)
1322: IN (>> 0x69) ADDR (0x3) EP (0x1)
1323: DATA1 (<< 0x4b) DATA(1 02 04 00)
**********
This is the data I see with the USB analyzer, but which usb_irq never gets.
> By the way, you could try looking at the data toggle values in your log
> (indicated by DT0 or DT1 next to the MaxLen values). They are supposed to
> alternate each time a new URB is submitted, and they should be reset to 0
> when the device is initialized and when the driver does a Clear Halt. I
> recently found the toggles were not getting set correctly for control
> transfers, so it's possible that something's going wrong with your
> interrupt transfers.
I have not log here, which shows the first and second run. It works in 2.4
and the driver does stop just the Int IN URB between runs, which is the same
it does in 2.4 and therefore I don't think, that anything can go wrong with
it.
Thanks
endergone Zwiebeltuete
-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
