From: Marcel Holtmann <marcel@holtmann.org>
To: Don Zickus <dzickus@redhat.com>
Cc: linux-bluetooth@vger.kernel.org, Oliver Neukum <oliver@neukum.org>
Subject: Re: [PATCH] btusb: typo in Broadcom SoftSailing id
Date: Thu, 29 Mar 2012 04:17:26 +0200 [thread overview]
Message-ID: <1332987446.1870.169.camel@aeonflux> (raw)
In-Reply-To: <1332967271-1743-1-git-send-email-dzickus@redhat.com>
Hi Don,
> I was trying to backport the following commit to RHEL-6
>
> From 0cea73465cd22373c5cd43a3edd25fbd4bb532ef Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oliver@neukum.org>
> Date: Wed, 21 Sep 2011 11:37:15 +0200
> Subject: [PATCH] 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:
>
> Bus 002 Device 003: ID 0a5c:21e1 Broadcom Corp.
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 1
> bDeviceProtocol 1
> bMaxPacketSize0 64
> idVendor 0x0a5c Broadcom Corp.
> idProduct 0x21e1
> bcdDevice 1.12
> iManufacturer 1 Broadcom Corp
> iProduct 2 BCM20702A0
> iSerial 3 60D819F0338C
> bNumConfigurations 1
>
> Looking at other Broadcom ids, the fix matches them whereas the original patch
> matches Apple's ids.
>
> Tested on an HP Elitebook 8760w. The btusb binds and the userspace stuff loads
> correctly.
>
> Cc: Oliver Neukum <oliver@neukum.org>
> Signed-off-by: Don Zickus <dzickus@redhat.com>
> ---
> drivers/bluetooth/btusb.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 789c9b5..86d9712 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -61,7 +61,7 @@ static struct usb_device_id btusb_table[] = {
> { USB_DEVICE_INFO(0xe0, 0x01, 0x01) },
>
> /* Broadcom SoftSailing reporting vendor specific */
> - { USB_DEVICE(0x05ac, 0x21e1) },
> + { USB_DEVICE(0x0a5c, 0x21e1) },
good catch. And this also should go into -stable as well.
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2012-03-29 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 20:41 [PATCH] btusb: typo in Broadcom SoftSailing id Don Zickus
2012-03-29 2:17 ` Marcel Holtmann [this message]
2012-03-29 10:45 ` Johan Hedberg
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=1332987446.1870.169.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=dzickus@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=oliver@neukum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox