I forgot to mention that only one of the BAPs run Bluetooth over USB,
the other one runs over a UART interface. (Both modules are CSR
however.)
The original setup looked like this:
(USB)(UART)
PC -- eth -- BAP1 -- bluetooth -- BAP2
where BAP1 acts as a bridge. So,
Greg KH wrote:
>
> 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 :(
Would sending a usb_clear_halt do the trick?
> I'd be interested as to why the stall happens, any ideas about th
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
