The patch titled
HCIUSB: Initialize the Broadcom USB Bluetooth device in Dell laptops
has been added to the -mm tree. Its filename is
hciusb-initialize-the-broadcom-usb-bluetooth-device-in-dell-laptops.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: HCIUSB: Initialize the Broadcom USB Bluetooth device in Dell laptops
From: Ben Collins <bcollins@xxxxxxxxxx>
Cc: Marcel Holtmann <marcel@xxxxxxxxxxxx>
Cc: Maxim Krasnyansky <maxk@xxxxxxxxxxxx>
Signed-off-by: Tim Gardner <tim.gardner@xxxxxxxxxx>
Signed-off-by: Phillip lougher <phillip@xxxxxxxxxx>
Signed-off-by: Ben Collins <bcollins@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/bluetooth/hci_usb.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/bluetooth/hci_usb.c~hciusb-initialize-the-broadcom-usb-bluetooth-device-in-dell-laptops drivers/bluetooth/hci_usb.c
--- a/drivers/bluetooth/hci_usb.c~hciusb-initialize-the-broadcom-usb-bluetooth-device-in-dell-laptops
+++ a/drivers/bluetooth/hci_usb.c
@@ -131,7 +131,7 @@ static struct usb_device_id blacklist_id
{ USB_DEVICE(0x03f0, 0x171d), .driver_info = HCI_WRONG_SCO_MTU },
/* Dell laptop with Broadcom chip */
- { USB_DEVICE(0x413c, 0x8126), .driver_info = HCI_WRONG_SCO_MTU },
+ { USB_DEVICE(0x413c, 0x8126), .driver_info = HCI_WRONG_SCO_MTU|HCI_RESET },
/* Microsoft Wireless Transceiver for Bluetooth 2.0 */
{ USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET },
_
Patches currently in -mm which might be from bcollins@xxxxxxxxxx are
origin.patch
avoid-zero-size-allocation-in-cache_k8_northbridges.patch
cleanup-libata-hpa-support.patch
hciusb-initialize-the-broadcom-usb-bluetooth-device-in-dell-laptops.patch
pm-do-not-require-dev-spew-to-get-pm_debug.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
