From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: [PATCH] Allow SCO with Asus WL-BTD202 dongle in btusb
Date: Tue, 28 Oct 2008 01:00:42 +0100 [thread overview]
Message-ID: <1225152042.17240.18.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Hello again,
This an other patch that allows my dongle to be configured correctly for
the voice/sco profile.
I already sent one for hci_usb some time ago, so it may sound familiar,
but it probably didn't have correct style...
Regards,
Guillaume B.
PS:
The HT-820 combo headset can now quite reliably use alternatively voice
and hi-fi profiles (and the keys).
This sometimes makes pulseaudio crash though.
Anyway, thanks for your hard work.
[-- Attachment #2: btusb-wl-btd202.patch --]
[-- Type: text/x-patch, Size: 856 bytes --]
This patch allows the 0b05:1715 Asus WL-BTD202 dongle to be used with a SCO
headset with having to specify "options btusb force_scofix=1".
Signed-off-by: Guillaume Bedot <littletux@zarb.org>
--- kernel-linus-2.6.28-0.rc1.1.1mdv.orig/drivers/bluetooth/btusb.c 2008-10-27 17:38:14.000000000 +0100
+++ kernel-linus-2.6.28-0.rc1.1.1mdv/drivers/bluetooth/btusb.c 2008-10-27 17:43:34.000000000 +0100
@@ -109,6 +109,9 @@
/* Apple MacBook Pro with Broadcom chip */
{ USB_DEVICE(0x05ac, 0x820f), .driver_info = BTUSB_RESET },
+ /* Asus dongle with Broadcom 2045 chip */
+ { USB_DEVICE(0x0b05, 0x1715), .driver_info = BTUSB_WRONG_SCO_MTU },
+
/* IBM/Lenovo ThinkPad with Broadcom chip */
{ USB_DEVICE(0x0a5c, 0x201e), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
{ USB_DEVICE(0x0a5c, 0x2110), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
next reply other threads:[~2008-10-28 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 0:00 Guillaume Bedot [this message]
2008-10-28 2:10 ` [PATCH] Allow SCO with Asus WL-BTD202 dongle in btusb Marcel Holtmann
2008-10-28 4:20 ` Guillaume Bedot
2008-11-30 10:46 ` Marcel Holtmann
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=1225152042.17240.18.camel@localhost \
--to=littletux@zarb.org \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.