I need a good explanation of what the proper HCD behavior in the following
situation is. If the HCD maintainers could tell me, I'd appreciate it.
Basically, I'm submitting an URB to get 256 bytes in from a bulk-in
endpoint. The device only has 36 to send. So it sends the 36.
Now, my understanding of the protocol is that the device will end that
transfer with either a short packet or a zero-length packet. So does the
completion handler get called immediately when the zero-length or short
packet it detected? Or am I seeing some sort of race-condition like bug in
my usb_stor_bulk_msg() function?
Perhaps someone who understands how this should work could take a look at
the usb_stor_bulk_msg() function and tell me if I'm doing something wrong
-- the code is based on the code in usb_bulk_msg(), but I may not have
gotten it right because I, quite frankly, don't understand the full
semantics of waitqueues.
Matt Dharm
--
Matthew Dharm Home: [EMAIL PROTECTED]
Senior Engineer, QCP Inc. Work: [EMAIL PROTECTED]
I want my GPFs!!!
-- Stef
User Friendly, 11/9/1998
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
