Date: 29 Nov 2005 04:22:23 +0000 From: faigozhu <faigozhu@fastmail.fm> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. Message-ID: <86r79013sw.fsf@fastmail.fm> In-Reply-To: <438BCE22.3050901@savvis.net> References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Maksim Yevmenkin <maksim.yevmenkin@savvis.net> writes: > [...] > > >> thanks. unfortunately, this binary dump did not reveal the problem. > >> i'd like you to try the following: > >> 1) reboot > >> 2) attach usb bluetooth dongle and start bluetooth stack > > # /etc/rc.bluetooth start ubt0 > > BD_ADDR: 00:0a:3a:63:de:86 > > Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> > > <Encryption> <Slot offset> > > <Timing accuracy> <Switch> <Hold mode> <Sniff mode> <RSSI> > > <Channel quality> <SCO link> <HV2 packets> <HV3 packets> > > <u-law log> <A-law log> <CVSD> <Power control> > > <Transparent SCO data> Max. ACL packet size: 377 bytes > > Number of ACL packets: 10 > > Max. SCO packet size: 16 bytes > > Number of SCO packets: 0 > > this looks good. number of sco packets == 0 is strange, but its not > your problem. i've seen this in other devices. is this a broadcom chip > based device? Yes. ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > >dmesg: > > [...] [...] > > > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! > > aha! this is your problem. usb bulk transfer failed. that explains why > sdpcontrol failed. bluetooth usb device use usb control transfers to > send hci command and usb interrupt transfers to receive hci > event. bulk usb transfers used to transfer the data. > > so, in your case, usb control/interrupt transfers with your device > work just fine. that explains why you can send commands to the device > and get responses back. however, as soon as you try to transfer data > (which require usb bulk transfer) the device chokes. that is why you > never see sdp response from the headset - it probably never saw the > sdp request, because bulk transfer failed and the data were never > transmitted over the radio. > > what is the model of your bluetooth usb dongle? are you using usb hub? > what is your usb controller type uhci, ohci or ehci? sigh, belkin again. It's a belkin bluetooth usb adapter, model F8T008. Another usb device is a usb mouse. Both of them directly connection to my laptop, no usb hub. dmesg|grep uhci uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0x1820-0x183f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0 uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0x1840-0x185f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1 uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0x1860-0x187f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2 %dmesg|grep ohci fwohci0: <VIA Fire II (VT6306)> port 0x3400-0x347f mem 0xe0200000-0xe02007ff irq 20 at device 0.0 on pci2 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:02:3f:3a:41:00:20:b8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: <IEEE1394(FireWire) bus> on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode %dmesg|grep echi % Is that any solution? Or, likely NDIS, to use windows native driver? > > thanks, > max > -- Many thanks, Faigozhu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r79013sw.fsf>