From: Perry Ismangil <ismangil@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Bluetooth USB dongle from Roper -- supported?
Date: Fri, 15 Apr 2005 11:36:47 +0100 [thread overview]
Message-ID: <a8f65f4b05041503367f9a46a7@mail.gmail.com> (raw)
I am using the bluez stack in kernel 2.6.10-1.770_FC3.
When I plugin the usb class 1 dongle, hciconfig -a came up with:
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT
And cat /proc/bus/usb/devices
T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 8 Spd=3D12 MxC=
h=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D1310 ProdID=3D0001 Rev=3D15.00
S: Manufacturer=3DSiW
S: Product=3DSiW
S: SerialNumber=3DF5CF040D0B00
C:* #Ifs=3D 2 Cfg#=3D 1 Atr=3Da0 MxPwr=3D 50mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
Since most how-tos assume that hciconfig came up with something
useful, I am now stuck. Any ideas?
Thanks.
--=20
Perry Ismangil
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-04-15 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 10:36 Perry Ismangil [this message]
2005-04-15 10:53 ` [Bluez-users] Bluetooth USB dongle from Roper -- supported? Michal Semler
2005-04-15 12:46 ` Perry Ismangil
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=a8f65f4b05041503367f9a46a7@mail.gmail.com \
--to=ismangil@gmail.com \
--cc=bluez-users@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