From: "Xuân Baldauf" <xuan--2006.11.06--bluez-devel--lists.sourceforge.net@baldauf.org>
To: marcel@holtmann.org, maxk@qualcomm.com
Cc: bluez-devel@lists.sourceforge.net
Subject: [patch] Broadcom BCM2045 SCO workaround
Date: Mon, 06 Nov 2006 18:35:35 +0100 [thread overview]
Message-ID: <454F7267.9010409@baldauf.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1537 bytes --]
Hello,
The Broadcom BCM2045 chipset seems to be also one of those chipsets
which report the SCO maximum packet incorrectly. The attached patch
works around this problem. With this workaround, a bluetooth USB dongle
with this chipset is able to send SCO data correctly.
The fix was verified using this USB dongle (MSI StarKey 2.0 (Ver 222-BW))
Bus 002 Device 004: ID 0a5c:2101 Broadcom Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x2101
bcdDevice 0.00
iManufacturer 1 Broadcom Corp
iProduct 2 BCM92045DG Non-UHE
iSerial 0
bNumConfigurations 1
and a Plantronics Explorer 320:
Device Name: 320 Plantronics
LMP Version: 1.2 (0x2) LMP Subversion: 0x8d1
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xbc 0xe8 0x01 0x00 0x08 0x08 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role
switch>
<sniff mode> <SCO link> <HV3 packets> <u-law log>
<A-law log>
<CVSD> <AFH cap. slave> <AFH cap. master
ciao,
Xuân.
P.S.: Maybe it is possible to leave out the "HCI_RESET" part of the
.driver_info field.
[-- Attachment #1.2: Type: text/html, Size: 3097 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix.BCM92045DG.SCOsendProblem.patch --]
[-- Type: text/x-patch; name="fix.BCM92045DG.SCOsendProblem.patch", Size: 616 bytes --]
Signed-off-by: Xuân Baldauf <xuan--2006.11.06--BCM2045-SCO-workaround@baldauf.org>
--- drivers/bluetooth/hci_usb.c.orig.0 2006-10-21 16:53:17.000000000 +0200
+++ drivers/bluetooth/hci_usb.c 2006-11-04 02:35:48.000000000 +0100
@@ -115,6 +115,9 @@
{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_WRONG_SCO_MTU },
{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_BCM92035 },
+ /* Broadcom BCM2045 */
+ { USB_DEVICE(0x0a5c, 0x2101), .driver_info = HCI_RESET | HCI_WRONG_SCO_MTU },
+
/* IBM/Lenovo ThinkPad with Broadcom chip */
{ USB_DEVICE(0x0a5c, 0x201e), .driver_info = HCI_WRONG_SCO_MTU },
next reply other threads:[~2006-11-06 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 17:35 Xuân Baldauf [this message]
2006-11-06 17:42 ` [Bluez-devel] [patch] Broadcom BCM2045 SCO workaround Marcel Holtmann
2006-11-06 20:08 ` Xuân Baldauf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=454F7267.9010409@baldauf.org \
--to=xuan--2006.11.06--bluez-devel--lists.sourceforge.net@baldauf.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox