From: Marcel Holtmann <marcel@holtmann.org>
To: Хедин <hedin@hiervard.ru>
Cc: bluez-users@lists.sf.net
Subject: Re: [Bluez-users] Re: Can't understand
Date: Thu, 13 May 2004 06:31:07 +0200 [thread overview]
Message-ID: <1084422667.25099.130.camel@pegasus> (raw)
In-Reply-To: <200405130659.45969.hedin@hiervard.ru>
Hi,
> // I guess, this one is dongle.
> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.01 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0a5c ProdID=2033 Rev= 0.a0
> C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
you guess right and it needs the bcm203x and the hci_usb driver. So when
do you start looking at the logfiles to see what is going wrong.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-13 4:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 23:59 [Bluez-users] Re: Can't understand Хедин
2004-05-13 4:31 ` Marcel Holtmann [this message]
[not found] ` <200405131627.34993.hedin@hiervard.ru>
2004-05-13 10:32 ` Nicholas A. Preyss
[not found] ` <200405131950.38279.hedin@hiervard.ru>
2004-05-13 16:33 ` Nicholas A. Preyss
2004-05-13 16:20 ` Xavier Garreau
2004-05-13 17:45 ` Nicholas A. Preyss
2004-05-13 21:54 ` Marcel Holtmann
2004-05-16 19:57 ` Nicholas A. Preyss
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=1084422667.25099.130.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sf.net \
--cc=hedin@hiervard.ru \
/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.