2005/10/11, Alan Stern <[EMAIL PROTECTED]>:
> Be more careful here. It doesn't hold urb->lock while _reading_
> urb->status; there's no point. But it does hold urb->lock while
> _writing_ urb->status. That is necessary.
>
hmm, sorry but I don't see why it needs a lock while writing but not
while reading...can you explain please ?
Another point in my hcd is that an urb can already be transfered by hw
before hcd->urb_enqueue method is called. Actually as soon as this urb
is linked into the corresponding ep's urb list, the hw can send it. Do
you think it can be an issue ?
I'm asking this question because I get sometime a warning on the
console saying:
"Badness in kref_get at lib/kref.c:32".
Thanks
--
Franck
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
