From: Oliver Neukum <oneukum@suse.de>
To: Jesse Sung <jesse.sung@canonical.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, 854399@bugs.launchpad.net
Subject: Re: [PATCH] Bluetooth: Add support for Broadcom BCM20702A0.
Date: Wed, 21 Sep 2011 10:45:22 +0200 [thread overview]
Message-ID: <201109211045.22997.oneukum@suse.de> (raw)
In-Reply-To: <4E794037.6090809@canonical.com>
Am Mittwoch, 21. September 2011, 03:39:03 schrieb Jesse Sung:
> > please prove that this is needed. What does usb-devices tell you about
> > this device?
>=20
> Hi Marcel,
>=20
> Currently I only have the output of lsusb -v at hand:
>=20
> Bus 001 Device 003: ID 413c:8197 Dell Computer Corp.
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 1
> bDeviceProtocol 1
> bMaxPacketSize0 64
> idVendor 0x413c Dell Computer Corp.
> idProduct 0x8197
> bcdDevice 1.12
> iManufacturer 1 Broadcom Corp
> iProduct 2 BCM20702A0
[..]
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
Hi,
this is really all you need. As soon as it reports that class, you need to =
have
the vendor:device in the driver to bind. Otherwise usbcore won't even probe.
Regards
Oliver
=2D-=20
=2D - -=20
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6r=
ffer, HRB 16746 (AG N=C3=BCrnberg)=20
Maxfeldstra=C3=9Fe 5 =20
90409 N=C3=BCrnberg=20
Germany=20
=2D - -=20
next prev parent reply other threads:[~2011-09-21 8:45 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 [this message]
2011-10-31 19:33 ` Gustavo Padovan
2011-11-08 6:51 ` Jesse Sung
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=201109211045.22997.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=854399@bugs.launchpad.net \
--cc=jesse.sung@canonical.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.