On Fri, Jun 28, 2002 at 02:35:16PM +0200, Orjan Friberg wrote: > > My second problem is that, after a while, the bulk out endpoint first > stops responding and then reports a stall. These conditions are > reported back in urb->status as -EPROTO and -EPIPE, respectively, but > the bluetooth_write_bulk_callback function simply returns for status != > 0. According to the USB Chief's error summary, there's no packet error > which would explain the lack of an ack/nak before the stall is > reported. Any idea on how to correct this error condition? It is up to > the device driver or the host driver?
It's up to the device driver to detect that the error was one that is recoverable, and to fix it. As you found out, the bluetooth.c driver does not do that :( I'd be interested as to why the stall happens, any ideas about that? > * Please note that the CRIS host driver in the official kernel is a > horrible, broken mess. Please send patches fixing this then :) thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
