From: Marcel Holtmann <marcel@holtmann.org>
To: Rudolf Matousek <matousek@utia.cas.cz>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] i-Tec Bluetooth USB dongle
Date: Tue, 10 Feb 2004 10:34:41 +0100 [thread overview]
Message-ID: <1076405681.32750.26.camel@pegasus> (raw)
In-Reply-To: <40289CAA.8050204@utia.cas.cz>
Hi Rudolf,
> I don't see any of these devices when dongle is unplugged. All these
> devices are definitely integrated in the dongle.
>
> I guess that the chip may be Broadcom 2035 (see serial no.).
>
> This is the output of the hciconfig:
>
> 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:3 acl:0 sco:0 commands:1 errors:0
>
> # hciconfig hci0 up
> Can't init device hci0. Connection timed out(110)
>
> # dmesg after dongle insertion
> hub.c: new USB device 00:07.2-2.4, assigned address 15
> hub.c: USB hub found
> hub.c: 3 ports detected
> hub.c: new USB device 00:07.2-2.4.1, assigned address 16
> hub.c: new USB device 00:07.2-2.4.2, assigned address 17
> input: USB HID v1.11 Keyboard [0a5c:0099] on usb1:17.0
> hub.c: new USB device 00:07.2-2.4.3, assigned address 18
> input: USB HID v1.11 Mouse [0a5c:0097] on usb1:18.0
>
> # /var/log/daemon.log removal and insertion
>
> Feb 10 09:54:22 Cipisek hcid[739]: HCI dev 0 unregistered
> Feb 10 09:54:36 Cipisek hcid[739]: HCI dev 0 registered
> Feb 10 09:54:46 Cipisek hcid[10193]: Can't init device hci0. Connection
> timed out(110)
>
> If you wish, I can create an account on my machine and you can try to
> dig in by yourself. Maybe you will be much more sucessful.
thanks for the offer, but I can't do anything without proper information
about these dongle. You must log the USB traffic on a Windows machine
with USB SnoopyPro (http://sourceforge.net/projects/usbsnoop/). There
must be some kind of firmware loading or switching stuff to make these
dongle working.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-10 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 7:00 [Bluez-users] i-Tec Bluetooth USB dongle Rudolf Matousek
2004-02-10 8:21 ` Marcel Holtmann
[not found] ` <402895E4.4040500@utia.cas.cz>
2004-02-10 8:33 ` Marcel Holtmann
[not found] ` <40289CAA.8050204@utia.cas.cz>
2004-02-10 9:34 ` Marcel Holtmann [this message]
[not found] ` <4028C63C.8070604@utia.cas.cz>
[not found] ` <1076450519.2777.1.camel@pegasus>
[not found] ` <4029E0D7.6010205@utia.cas.cz>
[not found] ` <1076506482.2777.91.camel@pegasus>
[not found] ` <402A3528.6090005@utia.cas.cz>
[not found] ` <1076519321.2696.61.camel@pegasus>
2004-02-13 7:31 ` Rudolf Matousek
2004-02-15 18:09 ` i-Tec Bluetooth USB dongle with CSR chip Zdzislaw A.Kaleta
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=1076405681.32750.26.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=matousek@utia.cas.cz \
/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