From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Asus WL-BTD202 needs force_scofix
Date: Mon, 28 Jan 2008 09:38:43 +0100 [thread overview]
Message-ID: <1201509523.7254.1.camel@localhost> (raw)
In-Reply-To: <1201344161.7769.28.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 74 bytes --]
Hello,
Hopefully, this time a working patch :-)
Regards,
Guillaume B.
[-- Attachment #2: hci_usb.c-automatically-set-scofix-for-wl-btd202-v2.patch --]
[-- Type: text/x-patch, Size: 437 bytes --]
--- drivers/bluetooth/hci_usb.c.orig 2008-01-28 02:43:22.000000000 +0100
+++ drivers/bluetooth/hci_usb.c 2008-01-28 00:34:12.000000000 +0100
@@ -104,6 +104,9 @@
MODULE_DEVICE_TABLE (usb, bluetooth_ids);
static struct usb_device_id blacklist_ids[] = {
+ /* ASUS WL-BTD202 */
+ { USB_DEVICE(0x0b05, 0x1715), .driver_info = HCI_WRONG_SCO_MTU },
+
/* CSR BlueCore devices */
{ USB_DEVICE(0x0a12, 0x0001), .driver_info = HCI_CSR },
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- 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
prev parent reply other threads:[~2008-01-28 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 8:47 [Bluez-devel] Asus WL-BTD202 needs force_scofix Guillaume Bedot
2008-01-22 11:37 ` [Bluez-devel] [PATCH][HFP] Support for CLIP Alok
2008-01-22 11:40 ` [Bluez-devel] Asus WL-BTD202 needs force_scofix Marcel Holtmann
2008-01-26 10:42 ` Guillaume Bedot
2008-01-28 8:38 ` Guillaume Bedot [this message]
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=1201509523.7254.1.camel@localhost \
--to=littletux@zarb.org \
--cc=bluez-devel@lists.sourceforge.net \
/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.