From: Marcel Holtmann <marcel@holtmann.org>
To: "Cufi, Carles" <carles.cufi@nordicsemi.no>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: btusb and non-standard descriptors
Date: Wed, 11 May 2011 18:32:13 -0700 [thread overview]
Message-ID: <1305163933.15916.170.camel@aeonflux> (raw)
In-Reply-To: <5B4B9A479BF6994B88EA975675EC5B790575861F5C@MES1OS2SXC003.mes1.tconet.net>
Hi Carles,
> Just wondering, what intefaces/endpoints does btusb use when there's no standard "USB_DEVICE_INFO(0xe0, 0x01, 0x01)" descriptor and instead it's using a hardcoded VID/PID?
the ones described in the Bluetooth USB HCI (aka H:2) standard.
Regards
Marcel
prev parent reply other threads:[~2011-05-12 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 13:25 btusb and non-standard descriptors Cufi, Carles
2011-05-12 1:32 ` Marcel Holtmann [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=1305163933.15916.170.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=carles.cufi@nordicsemi.no \
--cc=linux-bluetooth@vger.kernel.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