This is starting to make more sense now. I've been playing with the LEGO driver and
that's why I started asking these types of questions several days ago.
When the original urb is submitted, are you supposed to put 64 bytes in the urb, and
then 36 bytes in the next urb (you as in the driver wr
Right - that sounds like a good plan for a real driver. Using the usbdevfs code
however, if you call proc_reapurb() the completed request is freed before the call
returns to you, so there is still a chance the
urb will interrupt again before you get to cancel it.
since usbdevfs always frees th
I'm pleased I asked now. I had no idea that you could even submit a bulk URB to an
interrupt endpoint. I would have submitted an INT one and then probably fallen foul of
the very code you mention.
Perhaps that needs patching, so that the devfs code ensures that the urb is cancelled
before ret
I'm pleased I asked now. I had no idea that you could even submit a bulk URB to an
interrupt endpoint. I would have submitted an INT one and then probably fallen foul of
the very code you mention.
Perhaps that needs patching, so that the devfs code ensures that the urb is cancelled
before ret
