Hi Ben and Greg,
Please queue
2e8b506310f6 Bluetooth: btusb: typo in Broadcom SoftSailing id
for 3.0.y and 3.2.y. (The patch is already in 3.4, so no need to
apply it for newer kernels.)
It fixes a typo in a USB id. The symptom is that bluetooth does not
get activated on affected laptops.
The typo was noticed by Don Zickus[1]:
> I was trying to backport the following commit to RHEL-6
[c510eae377c7, "btusb: add device entry for Broadcom SoftSailing"]
> and noticed it wasn't working on an HP Elitebook. Looking into the patch I
> noticed a very subtle typo in the ids. The patch has '0x05ac' instead of
> '0x0a5c'. A snippet of the lsusb -v output also shows this:
Marcel Holtmann acked the fix for stable[2]:
> good catch. And this also should go into -stable as well.
>
> Acked-by: Marcel Holtmann <marcel@xxxxxxxxxxxx>
Later Ariel M Utuma ran into the same problem on a 3.2.y-based
kernel and confirmed that the fix works[3]:
> This is a minor but annoying bug,
> btusb on my HP Envy 15 laptop failed to activate bluetooth,
[...]
> I can confirm that patch number 4
> [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on
> my laptop.
The incorrect USB id was added in c510eae377c7 ("btusb: add device
entry for Broadcom SoftSailing", 2011-09-21). Those were the dark
ages when adding new ids to bluetooth drivers didn't require
usb-devices output. That patch was backported to 3.0.y so this fix
should go there, too.
Thanks,
Jonathan
[1] http://thread.gmane.org/gmane.linux.bluez.kernel/23367
[2] http://thread.gmane.org/gmane.linux.bluez.kernel/23367/focus=23374
[3] http://bugs.debian.org/674565
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
