Linux bluetooth development
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtmkramer@xs4all.nl>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] btusb.c add IMC Networks id 13d3:3404 (bcm20702A0)
Date: Tue, 11 Feb 2014 17:00:11 +0100	[thread overview]
Message-ID: <1392134411.2625.1.camel@develbox> (raw)
In-Reply-To: <F0885393-70B7-483B-8F97-C4AB73B451E6@holtmann.org>

Hi Marcel,

On Mon, 2014-02-10 at 10:33 -0800, Marcel Holtmann wrote:
> HI Jurgen,
> 
> > Attached patch adds support for IMC Networks (13d3:3404) to BCM20702A0
> > in btusb.c. This device is used on the Asrock Z87E-ITX motherboard.
> > Tested against 3.12.9.
> > 
> > diff -uNrp
> > linux-3.12.9-301.jk1.fc20.x86_64.orig/drivers/bluetooth/btusb.c
> > linux-3.12.9-301.jk1.fc20.x86_64.new/drivers/bluetooth/btusb.c
> > --- a/drivers/bluetooth/btusb.c	2014-02-10 11:35:08.976975562 +0100
> > +++ b/drivers/bluetooth/btusb.c	2014-02-10 11:37:03.864921122 +0100
> > @@ -106,6 +106,7 @@ static struct usb_device_id btusb_table[
> > 	{ USB_DEVICE(0x04ca, 0x2003) },
> > 	{ USB_DEVICE(0x0489, 0xe042) },
> > 	{ USB_DEVICE(0x413c, 0x8197) },
> > +	{ USB_DEVICE(0x13d3, 0x3404) },
> > 
> > 	/* Foxconn - Hon Hai */
> > 	{ USB_VENDOR_AND_INTERFACE_INFO(0x0489, 0xff, 0x01, 0x01) },
> > 
> > Signed-off-by: Jurgen Kramer <gtm.kramer@xs4all.nl>
> > 
> > Jurgen
> > <btusb-bcm20702a0-add-imc-networks.patch>
> 
> please send patches inline created from git-format-patch and include /sys/kernel/debug/usb/devices details for this device.
OK. I'll resend in a couple of days.

Regards,
Jurgen

      reply	other threads:[~2014-02-11 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 11:26 [PATCH] btusb.c add IMC Networks id 13d3:3404 (bcm20702A0) Jurgen Kramer
2014-02-10 18:33 ` Marcel Holtmann
2014-02-11 16:00   ` Jurgen Kramer [this message]

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=1392134411.2625.1.camel@develbox \
    --to=gtmkramer@xs4all.nl \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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