From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: hci_usb question
Date: Fri, 21 Jan 2005 13:22:00 +0100 [thread overview]
Message-ID: <1106310120.7955.45.camel@pegasus> (raw)
In-Reply-To: <pan.2005.01.21.01.42.29.140990@yahoo.com>
Hi Paul,
> > Also hci_usb creates 3 USB interfaces for my BT dongle. What are these 3
> > USB interfaces for ?
> >
>
> I just looked in the specs and some other places and found it:
>
> One bluetooth bulk endpoint
> One bluetooth isochronous endpoint
> One firmware upgrade endpoint
>
> And it seems that hci_usb only claims bluetooth USB Wireless Controller
> class E0, and firmware upgrade which is USB class FE is left unclaimed.
>
> So, if hic_usb would claim also USB class FE, then it would not appear as
> red in usbview.
ask the author of usbview or check its source code. I don't know what
red means.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-01-21 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 1:14 [Bluez-devel] hci_usb question Paul Ionescu
2005-01-21 1:42 ` [Bluez-devel] " Paul Ionescu
2005-01-21 12:22 ` 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=1106310120.7955.45.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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