Dear Maintainer,
This is a minor but annoying bug,
btusb on my HP Envy 15 laptop failed to activate bluetooth,
since it lacks the appropriate usb_device_id entry.
I would propose adding the entry for more convinience and usability.
Currently I have to use some commands to activate the bluetooth module
by adding the ID entry on related sysfs file.
Err, upon examining the code I found that the entry already existed in
current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks
like it is a typo error.
--- this is the original line ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x05ac, 0x21e1) },
--- it supposed to be like this (checked in 3.4 source) ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x0a5c, 0x21e1) },
--- this is the original line ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x05ac, 0x21e1) },
--- it supposed to be like this (checked in 3.4 source) ---
/* Broadcom SoftSailing reporting vendor specific */
{ USB_DEVICE(0x0a5c, 0x21e1) },
Thanks, hope it helps.
All the best.
-arief
-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (
debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 21 17:45:41 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=bebd9c63-74ba-43e2-a2fc-5e42f29a0a78 ro quiet
** Tainted: C (1024)
* Module from drivers/staging has been loaded.