linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-devel] Broadcom 2035 SCO question
@ 2006-07-11 18:59 Fabien Chevalier
  2006-07-11 19:04 ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Fabien Chevalier @ 2006-07-11 18:59 UTC (permalink / raw)
  To: BlueZ development


Hi all,

I recently purchased a class 1 "sweex" bluetooth USB dongle.  It has a 
broadcom bcm2035
usb chip( idVendor = 0x0a5c, idProduct = 0x200a). It advertises SCO 
mtu=16, sco packets = 0.
I tryed to use it with SCO, no luck.(I wasn't surprised by that, given 
sco packets = 0) Then i looked at hci usb driver and found it was in the 
blacklist, with HCI_BROKEN_ISOC.

I then removed it from this list, forced SCO mtu to 48 and packets 
number to 8 by hacking hci_event.c... and guess what, it works !!

So my question is: shouldn't this product marked as HCI_WRONG_SCO_MTU 
mtu instead of HCI_BROKEN_ISOC?

Cheers,

Fabien


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Broadcom 2035 SCO question
  2006-07-11 18:59 [Bluez-devel] Broadcom 2035 SCO question Fabien Chevalier
@ 2006-07-11 19:04 ` Marcel Holtmann
  2006-07-17  7:27   ` Fabien Chevalier
  0 siblings, 1 reply; 4+ messages in thread
From: Marcel Holtmann @ 2006-07-11 19:04 UTC (permalink / raw)
  To: BlueZ development

Hi Fabien,

> I recently purchased a class 1 "sweex" bluetooth USB dongle.  It has a 
> broadcom bcm2035
> usb chip( idVendor = 0x0a5c, idProduct = 0x200a). It advertises SCO 
> mtu=16, sco packets = 0.
> I tryed to use it with SCO, no luck.(I wasn't surprised by that, given 
> sco packets = 0) Then i looked at hci usb driver and found it was in the 
> blacklist, with HCI_BROKEN_ISOC.
> 
> I then removed it from this list, forced SCO mtu to 48 and packets 
> number to 8 by hacking hci_event.c... and guess what, it works !!
> 
> So my question is: shouldn't this product marked as HCI_WRONG_SCO_MTU 
> mtu instead of HCI_BROKEN_ISOC?

is it enough to change HCI_BROKEN_ISOC into HCI_WRONG_SCO_MTU to make
this work. If yes, then I am happy to submit a patch.

Regards

Marcel




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Broadcom 2035 SCO question
  2006-07-11 19:04 ` Marcel Holtmann
@ 2006-07-17  7:27   ` Fabien Chevalier
  2006-07-18 17:12     ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Fabien Chevalier @ 2006-07-17  7:27 UTC (permalink / raw)
  To: BlueZ development

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

Hi All,

Please see comments below :

> Hi Fabien,
> 
>> I recently purchased a class 1 "sweex" bluetooth USB dongle.  It has a 
>> broadcom bcm2035
>> usb chip( idVendor = 0x0a5c, idProduct = 0x200a). It advertises SCO 
>> mtu=16, sco packets = 0.
>> I tryed to use it with SCO, no luck.(I wasn't surprised by that, given 
>> sco packets = 0) Then i looked at hci usb driver and found it was in the 
>> blacklist, with HCI_BROKEN_ISOC.
>>
>> I then removed it from this list, forced SCO mtu to 48 and packets 
>> number to 8 by hacking hci_event.c... and guess what, it works !!
>>
>> So my question is: shouldn't this product marked as HCI_WRONG_SCO_MTU 
>> mtu instead of HCI_BROKEN_ISOC?
> 
> is it enough to change HCI_BROKEN_ISOC into HCI_WRONG_SCO_MTU to make
> this work. If yes, then I am happy to submit a patch.
> 

Yes. It is not perfect (i have some noise sometimes at startup), but it
is enough to make it work.

Please find attached one-line patch for this.

cheers,

Fabien


[-- Attachment #2: patch-bcm2035.diff --]
[-- Type: text/plain, Size: 489 bytes --]

--- hci_usb.c	2006-07-15 15:32:34.000000000 +0200
+++ hci_usb.c	2006-07-15 15:32:47.000000000 +0200
@@ -108,7 +108,7 @@
 	{ USB_DEVICE(0x0a5c, 0x2033), .driver_info = HCI_IGNORE },
 
 	/* Broadcom BCM2035 */
-	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
+	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_WRONG_SCO_MTU },
 	{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_BCM92035 },
 
 	/* Microsoft Wireless Transceiver for Bluetooth 2.0 */


[-- Attachment #3: Type: text/plain, Size: 375 bytes --]


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] Broadcom 2035 SCO question
  2006-07-17  7:27   ` Fabien Chevalier
@ 2006-07-18 17:12     ` Marcel Holtmann
  0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2006-07-18 17:12 UTC (permalink / raw)
  To: BlueZ development

Hi Fabien,

> >> I recently purchased a class 1 "sweex" bluetooth USB dongle.  It has a 
> >> broadcom bcm2035
> >> usb chip( idVendor = 0x0a5c, idProduct = 0x200a). It advertises SCO 
> >> mtu=16, sco packets = 0.
> >> I tryed to use it with SCO, no luck.(I wasn't surprised by that, given 
> >> sco packets = 0) Then i looked at hci usb driver and found it was in the 
> >> blacklist, with HCI_BROKEN_ISOC.
> >>
> >> I then removed it from this list, forced SCO mtu to 48 and packets 
> >> number to 8 by hacking hci_event.c... and guess what, it works !!
> >>
> >> So my question is: shouldn't this product marked as HCI_WRONG_SCO_MTU 
> >> mtu instead of HCI_BROKEN_ISOC?
> > 
> > is it enough to change HCI_BROKEN_ISOC into HCI_WRONG_SCO_MTU to make
> > this work. If yes, then I am happy to submit a patch.
> > 
> 
> Yes. It is not perfect (i have some noise sometimes at startup), but it
> is enough to make it work.
> 
> Please find attached one-line patch for this.

a patch for this is in my tree now.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-07-18 17:12 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-11 18:59 [Bluez-devel] Broadcom 2035 SCO question Fabien Chevalier
2006-07-11 19:04 ` Marcel Holtmann
2006-07-17  7:27   ` Fabien Chevalier
2006-07-18 17:12     ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).