btusb and non-standard descriptors

Linux bluetooth development
 help / color / mirror / Atom feed

* btusb and non-standard descriptors
@ 2011-05-10 13:25 Cufi, Carles
  2011-05-12  1:32 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Cufi, Carles @ 2011-05-10 13:25 UTC (permalink / raw)
  To: linux-bluetooth@vger.kernel.org

Hi there,

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?

Thanks!

--
Carles

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: btusb and non-standard descriptors
  2011-05-10 13:25 btusb and non-standard descriptors Cufi, Carles
@ 2011-05-12  1:32 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2011-05-12  1:32 UTC (permalink / raw)
  To: Cufi, Carles; +Cc: linux-bluetooth@vger.kernel.org

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-05-12  1:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-10 13:25 btusb and non-standard descriptors Cufi, Carles
2011-05-12  1:32 ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox