[Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

My new USB dongle (MyCom label, but it's a Broadcom) does not work with
Linux Debian (unstable) kernel 2.4.27 or 2.6.8 and bluez-utils 2.10-1
(Debian package). It loads, but scanning does not work.

p2:~# hciconfig -a
hci0:   Type: USB
        BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
        UP RUNNING 
        RX bytes:163 acl:0 sco:0 events:21 errors:0  
        TX bytes:583 acl:0 sco:0 commands:21 errors:0
        Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT 
Can't read local name on hci0. Input/output error(5)


p2:~# hciconfig hci0 version
hci0:   Type: USB
        BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
        HCI Ver: 1.2 (0x2) HCI Rev: 0x69 LMP Ver: 1.2 (0x2) LMP Subver:
0x694a
        Manufacturer: Broadcom Corporation (15)

p2:~# hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
        Firmware 105.105.074

p2:~# lsusb
Bus 001 Device 009: ID 0a5c:3503 Broadcom Corp.
Bus 001 Device 008: ID 0a5c:3502 Broadcom Corp.
Bus 001 Device 007: ID 0a5c:2009 Broadcom Corp.
Bus 001 Device 006: ID 0a5c:3535 Broadcom Corp.
Bus 001 Device 001: ID 0000:0000

hcid says:
  hcid[6544]: Can't set scan mode on hci0. Device or resource busy(16)
  hcid[6544]: Can't set auth on hci0. Device or resource busy(16)   
  hcid[6544]: Can't set encrypt on hci0. Device or resource busy(16)

I guess these happen, because there are 4 devices instead of just one (as
with my MSI dongle, that works fins).

Tried to change to HCI:

p2:~# hid2hci --tohci
No devices in HCI mode found

Installed packages: 
ii  bluez-bluefw   1.0-1          Firmware and loader for BCM2033-based ...
ii  bluez-hcidump  1.12-1         Analyses Bluetooth HCI packets
ii  bluez-pin      0.24-1         Bluetooth PIN helper with D-BUS support
ii  bluez-utils    2.10-1         Bluetooth tools and daemons

Any ideas?

Or should I better swap the device for a (more expensive) MSI ?

I'm compiling kernel 2.6.9, now. Maybe that helps?

Hans


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]

Hi Hans,

> My new USB dongle (MyCom label, but it's a Broadcom) does not work with
> Linux Debian (unstable) kernel 2.4.27 or 2.6.8 and bluez-utils 2.10-1
> (Debian package). It loads, but scanning does not work.
> 
> p2:~# hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
>         UP RUNNING 
>         RX bytes:163 acl:0 sco:0 events:21 errors:0  
>         TX bytes:583 acl:0 sco:0 commands:21 errors:0
>         Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT 
> Can't read local name on hci0. Input/output error(5)
> 
> 
> p2:~# hciconfig hci0 version
> hci0:   Type: USB
>         BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
>         HCI Ver: 1.2 (0x2) HCI Rev: 0x69 LMP Ver: 1.2 (0x2) LMP Subver:
> 0x694a
>         Manufacturer: Broadcom Corporation (15)
> 
> p2:~# hciconfig hci0 revision
> hci0:   Type: USB
>         BD Address: 00:02:72:C0:11:1C ACL MTU: 377:10  SCO MTU: 16:0
>         Firmware 105.105.074
> 
> p2:~# lsusb
> Bus 001 Device 009: ID 0a5c:3503 Broadcom Corp.
> Bus 001 Device 008: ID 0a5c:3502 Broadcom Corp.
> Bus 001 Device 007: ID 0a5c:2009 Broadcom Corp.
> Bus 001 Device 006: ID 0a5c:3535 Broadcom Corp.
> Bus 001 Device 001: ID 0000:0000

please send us the content of /proc/bus/usb/devices and you can try the
attached patch.

> Or should I better swap the device for a (more expensive) MSI ?

The CSR based dongles actually make less problems. If you don't need it
anymore, you can donate it to me, because I really need these kind of
dongles for testing.

Regards

Marcel


[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 687 bytes --]

===== drivers/bluetooth/hci_usb.c 1.58 vs edited =====
--- 1.58/drivers/bluetooth/hci_usb.c	2004-10-27 23:42:21 +02:00
+++ edited/drivers/bluetooth/hci_usb.c	2004-10-30 13:42:04 +02:00
@@ -101,8 +101,12 @@
 	{ USB_DEVICE(0x0a5c, 0x2033), .driver_info = HCI_IGNORE },
 
 	/* Broadcom BCM2035 */
+	{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
 	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
 
+	/* Microsoft Wireless Transceiver for Bluetooth 2.0 */
+	{ USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
+
 	/* ISSC Bluetooth Adapter v3.1 */
 	{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET },
 

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 01:47:57PM +0200, Marcel Holtmann wrote:
> 
> please send us the content of /proc/bus/usb/devices and you can try the
> attached patch.

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
....................(the host controller) ...........

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 3
.....................(other sys).................

T:  Bus=01 Lev=02 Prnt=06 Port=00 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a5c ProdID=2009 Rev= 1.00
S:  Manufacturer=Broadcom
S:  Product=BCM92035DGL
S:  SerialNumber=000272C0111C
C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

T:  Bus=01 Lev=02 Prnt=06 Port=01 Cnt=02 Dev#=  8 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=3502 Rev= 1.00
S:  SerialNumber=000272C0111C
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=01 Lev=02 Prnt=06 Port=02 Cnt=03 Dev#=  9 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=3503 Rev= 1.00
S:  SerialNumber=000272C0111C
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms
 
> The CSR based dongles actually make less problems. If you don't need it
> anymore, you can donate it to me, because I really need these kind of
> dongles for testing.

i'll keep it in mind

Kernel 2.6.10rc1 + patch is compiling now...

Hans
  



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > please send us the content of /proc/bus/usb/devices and you can try the
> > attached patch.
> 
> T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
> ....................(the host controller) ...........
> 
> T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 3
> .....................(other sys).................
> 
> T:  Bus=01 Lev=02 Prnt=06 Port=00 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> P:  Vendor=0a5c ProdID=2009 Rev= 1.00
> S:  Manufacturer=Broadcom
> S:  Product=BCM92035DGL
> S:  SerialNumber=000272C0111C
> C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
> I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
> I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
> I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
> 
> T:  Bus=01 Lev=02 Prnt=06 Port=01 Cnt=02 Dev#=  8 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0a5c ProdID=3502 Rev= 1.00
> S:  SerialNumber=000272C0111C
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
> E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
> 
> T:  Bus=01 Lev=02 Prnt=06 Port=02 Cnt=03 Dev#=  9 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0a5c ProdID=3503 Rev= 1.00
> S:  SerialNumber=000272C0111C
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
> E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

any additional information about this dongle? Link to a website or so?
 
> > The CSR based dongles actually make less problems. If you don't need it
> > anymore, you can donate it to me, because I really need these kind of
> > dongles for testing.
> 
> i'll keep it in mind
> 
> Kernel 2.6.10rc1 + patch is compiling now...

Does it work? If yes, send in the output from "hciconfig -a".

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 03:41:32PM +0200, Marcel Holtmann wrote:
> 
> any additional information about this dongle? Link to a website or so?

Made by Widcomm, inc.

Bluetooth v1.2 Compliant  

I've searched the manual (pdf) for 'http' and 'ftp' with no results.

> > > The CSR based dongles actually make less problems. If you don't need it
> > > anymore, you can donate it to me, because I really need these kind of
> > > dongles for testing.
> > 
> > i'll keep it in mind
> > 
> > Kernel 2.6.10rc1 + patch is compiling now...
> 
> Does it work? If yes, send in the output from "hciconfig -a".

No, down, no m

hci0:   Type: USB
        BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
        DOWN 
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:0 acl:0 sco:0 commands:0 errors:0
        Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DH1 HV1 
        Link policy: 
        Link mode: SLAVE ACCEPT 

p2:/var/log# hciconfig dev hci0 up
Can't init device hci0. Device or resource busy(16)

Hans


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > any additional information about this dongle? Link to a website or so?
> 
> Made by Widcomm, inc.
> 
> Bluetooth v1.2 Compliant  
> 
> I've searched the manual (pdf) for 'http' and 'ftp' with no results.

and where did you bought it? What did it cost?

> > > Kernel 2.6.10rc1 + patch is compiling now...
> > 
> > Does it work? If yes, send in the output from "hciconfig -a".
> 
> No, down, no m
> 
> hci0:   Type: USB
>         BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
>         DOWN 
>         RX bytes:0 acl:0 sco:0 events:0 errors:0
>         TX bytes:0 acl:0 sco:0 commands:0 errors:0
>         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DH1 HV1 
>         Link policy: 
>         Link mode: SLAVE ACCEPT 
> 
> p2:/var/log# hciconfig dev hci0 up
> Can't init device hci0. Device or resource busy(16)

This is funny. Actually it should work fine with that patch. I included
it into 2.6.9-mh3 that I put out some minutes ago. Please try it again.

Maybe you wanna try to play with other combinations of the HCI_RESET and
HCI_BROKEN_ISOC quirks.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 05:42:38PM +0200, Marcel Holtmann wrote:
> Hi Hans,
> 
> > > any additional information about this dongle? Link to a website or so?
> > 
> > Made by Widcomm, inc.
> > 
> > Bluetooth v1.2 Compliant  
> > 
> > I've searched the manual (pdf) for 'http' and 'ftp' with no results.
> 
> and where did you bought it? What did it cost?

I have bought it at MyCom, Amsterdam: http://www.mycom.nl/index.html
for 25 euro.

http://silverapp1.mycom.nl/MyCom/Store/productdetailedinfo.do?productID=71950&productType=1

I also have the MSI adapter:
  http://silverapp1.mycom.nl/MyCom/Store/productdetailedinfo.do?productID=35060&productType=1

(I want one at work and at home. The MSI works fine.)

> > > > Kernel 2.6.10rc1 + patch is compiling now...
> > > 
> > > Does it work? If yes, send in the output from "hciconfig -a".
> > 
> > No, down, no m
> > 
> > hci0:   Type: USB
> >         BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
> >         DOWN 
> >         RX bytes:0 acl:0 sco:0 events:0 errors:0
> >         TX bytes:0 acl:0 sco:0 commands:0 errors:0
> >         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> >         Packet type: DM1 DH1 HV1 
> >         Link policy: 
> >         Link mode: SLAVE ACCEPT 
> > 
> > p2:/var/log# hciconfig dev hci0 up
> > Can't init device hci0. Device or resource busy(16)
> 
> This is funny. Actually it should work fine with that patch. I included
> it into 2.6.9-mh3 that I put out some minutes ago. Please try it again.
> 
> Maybe you wanna try to play with other combinations of the HCI_RESET and
> HCI_BROKEN_ISOC quirks.

It may be something else. I'll first try an unpatched kernel with the same
settings. The previous results were with the standard Debian kernel.

Hans



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > > > > Kernel 2.6.10rc1 + patch is compiling now...
> > > > 
> > > > Does it work? If yes, send in the output from "hciconfig -a".
> > > 
> > > No, down, no m
> > > 
> > > hci0:   Type: USB
> > >         BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
> > >         DOWN 
> > >         RX bytes:0 acl:0 sco:0 events:0 errors:0
> > >         TX bytes:0 acl:0 sco:0 commands:0 errors:0
> > >         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> > >         Packet type: DM1 DH1 HV1 
> > >         Link policy: 
> > >         Link mode: SLAVE ACCEPT 
> > > 
> > > p2:/var/log# hciconfig dev hci0 up
> > > Can't init device hci0. Device or resource busy(16)
> > 
> > This is funny. Actually it should work fine with that patch. I included
> > it into 2.6.9-mh3 that I put out some minutes ago. Please try it again.
> > 
> > Maybe you wanna try to play with other combinations of the HCI_RESET and
> > HCI_BROKEN_ISOC quirks.
> 
> It may be something else. I'll first try an unpatched kernel with the same
> settings. The previous results were with the standard Debian kernel.

actually there must be a secret within the init sequence of the commands
and you should try a clean 2.6.9 vanilla kernel with the -mh3 patch. I
think I will get this dongle working, but I need it at home for further
testing and I stopped buying Bluetooth dongles by myself. If you believe
it or not, I have enough of them ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 06:10:11PM +0200, Marcel Holtmann wrote:
> 
> actually there must be a secret within the init sequence of the commands
> and you should try a clean 2.6.9 vanilla kernel with the -mh3 patch.    
 
same results

p2:~# hciconfig dev hci0 up
Can't init device hci0. Device or resource busy(16)

And then I plugged in the other MSI (CSR) dongle: still works fine.

> I think I will get this dongle working, but I need it at home for further
> testing and I stopped buying Bluetooth dongles by myself. If you believe
> it or not, I have enough of them ;)

I think about returning it to the shop and buying the Cambridge-based
dongle. Let me know if I can try anything. I'll have it until tuesday, at
least.

Would it help to turn on CONFIG_BT_HCIUSB_DEBUG and examine log ?
 
Regards

Hans


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > actually there must be a secret within the init sequence of the commands
> > and you should try a clean 2.6.9 vanilla kernel with the -mh3 patch.    
>  
> same results
> 
> p2:~# hciconfig dev hci0 up
> Can't init device hci0. Device or resource busy(16)
> 
> And then I plugged in the other MSI (CSR) dongle: still works fine.
> 
> > I think I will get this dongle working, but I need it at home for further
> > testing and I stopped buying Bluetooth dongles by myself. If you believe
> > it or not, I have enough of them ;)
> 
> I think about returning it to the shop and buying the Cambridge-based
> dongle. Let me know if I can try anything. I'll have it until tuesday, at
> least.
> 
> Would it help to turn on CONFIG_BT_HCIUSB_DEBUG and examine log ?

I don't think so, because this is some kind of init problem. You can try
to set the quirk for your device 0a5c:2009 to HCI_BROKEN_ISOC only,
because it seems that parts of it still work if you don't call reset.
Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
yes, then try without it.

The other thing is to change the init sequence of HCI commands and
actually for this I must have this dongle at home. Think about donating
it to me instead of returning it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 10:23:09PM +0200, Marcel Holtmann wrote:
> 
> I don't think so, because this is some kind of init problem. You can try
> to set the quirk for your device 0a5c:2009 to HCI_BROKEN_ISOC only,
> because it seems that parts of it still work if you don't call reset.

Did this, but with same result. I only compiled 'hci_usb.c' and replaced the
'hci_usb.ko' since it's only a piece of implementation that changed. Must be
OK, I guess.

> Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
> yes, then try without it.

OK, maybe this is the problem. The Debian default was with
CONFIG_BT_HCIUSB_SCO=y, so I kept that.

Now I have to recompile everything, I guess.
It's compiling on the 2.8 GHz P4 machine at my work, now.

> The other thing is to change the init sequence of HCI commands and
> actually for this I must have this dongle at home. Think about donating
> it to me instead of returning it.

Maybe I'll buy another one for you, if I think it will work. 


Hans


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Sat, Oct 30, 2004 at 10:23:09PM +0200, Marcel Holtmann wrote:
> Hi Hans,
> 
> > > actually there must be a secret within the init sequence of the commands
> > > and you should try a clean 2.6.9 vanilla kernel with the -mh3 patch.    
> >  
> > same results
> > 
> > p2:~# hciconfig dev hci0 up
> > Can't init device hci0. Device or resource busy(16)
> > 
> > And then I plugged in the other MSI (CSR) dongle: still works fine.
> > 
> > > I think I will get this dongle working, but I need it at home for further
> > > testing and I stopped buying Bluetooth dongles by myself. If you believe
> > > it or not, I have enough of them ;)
> > 
> > I think about returning it to the shop and buying the Cambridge-based
> > dongle. Let me know if I can try anything. I'll have it until tuesday, at
> > least.
> > 
> > Would it help to turn on CONFIG_BT_HCIUSB_DEBUG and examine log ?
> 
> I don't think so, because this is some kind of init problem. You can try
> to set the quirk for your device 0a5c:2009 to HCI_BROKEN_ISOC only,
> because it seems that parts of it still work if you don't call reset.
> Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
> yes, then try without it.

Maybe I've missed something here, but I cannot see how this HCI_BROKEN_ISOC
bit can do anything if CONFIG_BT_HCIUSB_SCO is off, because it's only used
inside the CONFIG_BT_HCIUSB_SCO ifdef.

  #ifdef CONFIG_BT_HCIUSB_SCO
	if (!(id->driver_info & HCI_BROKEN_ISOC))
		isoc_iface = usb_ifnum_to_if(udev, isoc_ifnum);

 
> The other thing is to change the init sequence of HCI commands and
> actually for this I must have this dongle at home. Think about donating
> it to me instead of returning it.

I asked MyCom to send one to you. I hope my arguments were good enough.

regards,

Hans

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > > Would it help to turn on CONFIG_BT_HCIUSB_DEBUG and examine log ?
> > 
> > I don't think so, because this is some kind of init problem. You can try
> > to set the quirk for your device 0a5c:2009 to HCI_BROKEN_ISOC only,
> > because it seems that parts of it still work if you don't call reset.
> > Btw do you compiled your kernel with the CONFIG_BT_HCIUSB_SCO option? If
> > yes, then try without it.
> 
> Maybe I've missed something here, but I cannot see how this HCI_BROKEN_ISOC
> bit can do anything if CONFIG_BT_HCIUSB_SCO is off, because it's only used
> inside the CONFIG_BT_HCIUSB_SCO ifdef.
> 
>   #ifdef CONFIG_BT_HCIUSB_SCO
> 	if (!(id->driver_info & HCI_BROKEN_ISOC))
> 		isoc_iface = usb_ifnum_to_if(udev, isoc_ifnum);

you are right. If CONFIG_BT_HCIUSB_SCO is disabled then the value of
HCI_BROKEN_ISOC doesn't matters.
 
> > The other thing is to change the init sequence of HCI commands and
> > actually for this I must have this dongle at home. Think about donating
> > it to me instead of returning it.
> 
> I asked MyCom to send one to you. I hope my arguments were good enough.

I don't expect to get one from them. Some companies have some stupid
rules for test hardware for open source developers. And actually I think
this is a Broadcom problem, because they are not very helpful when it
comes to Linux support. On the other hand you get CSR and these guys
helped out in so many ways. Go and buy a CSR based dongle, because this
is better spent money and you will have less trouble.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Hans Bausewein]

On Tue, Nov 02, 2004 at 10:58:16PM +0100, Marcel Holtmann wrote:
> I don't expect to get one from them. Some companies have some stupid
> rules for test hardware for open source developers. And actually I think
> this is a Broadcom problem, because they are not very helpful when it
> comes to Linux support. On the other hand you get CSR and these guys
> helped out in so many ways. Go and buy a CSR based dongle, because this
> is better spent money and you will have less trouble.

R&D at MyCom has tested the new dongle using RedHat 9 and it worked.
Maybe it is a problem with other software from Debian (or just my
configuration). I have to be at home to check this. The computer is off.

I'd like to ask them some more details. Exact versions of the kernel and
bluez-utils. More? Maybe some output from hciconfig?

Hans


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users

Re: [Bluez-users] Broadcom Corporation (Firmware 105.105.074) USB dongle

[Marcel Holtmann]

Hi Hans,

> > I don't expect to get one from them. Some companies have some stupid
> > rules for test hardware for open source developers. And actually I think
> > this is a Broadcom problem, because they are not very helpful when it
> > comes to Linux support. On the other hand you get CSR and these guys
> > helped out in so many ways. Go and buy a CSR based dongle, because this
> > is better spent money and you will have less trouble.
> 
> R&D at MyCom has tested the new dongle using RedHat 9 and it worked.
> Maybe it is a problem with other software from Debian (or just my
> configuration). I have to be at home to check this. The computer is off.

the RedHat 9 is very old and I think it is 2.4 based, where an old USB
subsystem and Bluetooth subsystem is used.

> I'd like to ask them some more details. Exact versions of the kernel and
> bluez-utils. More? Maybe some output from hciconfig?

Kernel version and the version of the bluez-* packages is enough.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users