Re: [PATCH] for ng_ubt2 stalled transfers

On Fri, Jan 23, 2009 at 03:21:21PM -0800, Maksim Yevmenkin wrote:
> > Thanks for the quick patch, but that did not help:
> >
> > ubt0: <Broadcom Corp Foxconn Bluetooth 2.0 plus EDR, class 224/1, rev 2.00/1.00, addr 2> on usbus2
> > ubt0:ubt_bulk_read_callback:981: bulk-in transfer failed: USB_ERR_STALLED
> > ubt0:ubt_intr_read_callback:834: interrupt transfer failed: USB_ERR_STALLED
> 
> stalled transfers are NOT going to be fixed. the patch was to make
> sure the system would not crash with stalled transfers.

Yes, that's working now. Thanks. BTW what are stalled transfers and does
that do any harm?

> > I also have another usb bluetooth stick which shows this on insertion:
> >
> > Jan 23 22:13:00 maggie kernel: usb2_alloc_device:1401: set address 2 failed (ignored)
> > Jan 23 22:13:00 maggie kernel: usb2_alloc_device:1436: getting device descriptor at addr 2 failed!
> 
> this is something else. this happens earlier than usb2_bluetooth_ng


Okay...

> 
> > Jan 23 22:13:01 maggie kernel: ugen0.2: <Cambridge Silicon Radio> at usbus0
> > Jan 23 22:13:01 maggie kernel: ubt1: <Cambridge Silicon Radio Bluetooth USB dongle, class 224/1, rev 1.10/3.73, addr 2> on usbus0
> 
> that looks normal to me.

Yup, it's working now with hccontrol -n ubt0hci inquiry