linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Sung <jesse.sung@canonical.com>
To: linux-bluetooth@vger.kernel.org, 854399@bugs.launchpad.net,
	padovan@profusion.mobi
Subject: Re: [PATCH] Bluetooth: Add support for Broadcom BCM20702A0.
Date: Tue, 08 Nov 2011 14:51:52 +0800	[thread overview]
Message-ID: <4EB8D188.2040407@canonical.com> (raw)
In-Reply-To: <20111031193354.GG10164@joana>

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

On 11/01/2011 03:33 AM, Gustavo Padovan wrote:
> Hi Jesse,
>
> * Jesse Sung<jesse.sung@canonical.com>  [2011-09-20 15:29:19 +0800]:
>
>> Add a new entry (413c:8197) to device ID table.
>
> Can I get the output of usbdevices in the commit message, please. Then we can
> prove that adding it to the device ID table is really necessary.
>
> 	Gustavo

Hi Gustavo,

Sure! Modified patch attached. :)

Thanks,
Jesse


[-- Attachment #2: 0001-Bluetooth-Add-support-for-Broadcom-BCM20702A0.patch --]
[-- Type: text/x-patch, Size: 1511 bytes --]

>From 7ced2be26f17eadc63c6b7fe0d37f948d4fef87c Mon Sep 17 00:00:00 2001
From: Wen-chien Jesse Sung <jesse.sung@canonical.com>
Date: Tue, 8 Nov 2011 14:30:22 +0800
Subject: [PATCH] Bluetooth: Add support for Broadcom BCM20702A0

Since this device declares itself as vendor specific, must add
a new entry to device ID table to support it.

usb-device output of this device:

T:  Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=413c ProdID=8197 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=D0DF9AA9C9F1
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

Signed-off-by: Wen-chien Jesse Sung <jesse.sung@canonical.com>
---
 drivers/bluetooth/btusb.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 9db2476..151a2d2 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -100,6 +100,9 @@ static struct usb_device_id btusb_table[] = {
 	/* Canyon CN-BTU1 with HID interfaces */
 	{ USB_DEVICE(0x0c10, 0x0000) },
 
+	/* Broadcom BCM20702A0 */
+	{ USB_DEVICE(0x413c, 0x8197) },
+
 	{ }	/* Terminating entry */
 };
 
-- 
1.7.7.1


  reply	other threads:[~2011-11-08  6:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  7:29 [PATCH] Bluetooth: Add support for Broadcom BCM20702A0 Jesse Sung
2011-09-20 13:05 ` Marcel Holtmann
2011-09-21  1:39   ` Jesse Sung
2011-09-21  7:53     ` Marcel Holtmann
2011-09-21 14:57       ` Jesse Sung
2011-10-25  8:41         ` Jesse Sung
2011-09-21  8:45     ` Oliver Neukum
2011-10-31 19:33 ` Gustavo Padovan
2011-11-08  6:51   ` Jesse Sung [this message]
2011-11-08 15:34     ` Gustavo Padovan

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=4EB8D188.2040407@canonical.com \
    --to=jesse.sung@canonical.com \
    --cc=854399@bugs.launchpad.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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;
as well as URLs for NNTP newsgroup(s).