From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcidump with multiple dongles
Date: Thu, 28 Jun 2007 16:57:35 +0200 [thread overview]
Message-ID: <1183042655.9499.22.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <2EB6297382462046A9427D7324788A4801F55370@MCLNEXVS06.resource.ds.bah.com>
Hi Richard,
> I've been working on a project that requires multiple Bluetooth
> dongles on a single PC. I have a USB 2.0 hub with two dongles. I can
> create my problem in the following manner:
>
> - window 1 l2ping xx:xx:xx:xx:xx:xx - so this command is running
> constantly.
> - window 2 hcidump -i hci0 - this command is dumping
> the output correctly.
> - window 3 hcitool scan -i hci1
this must be hcitool -i hci1 scan.
> - window 4 hcidump -i hci1
>
> After a little while ( sometimes immediately ) the hcitool scan in
> window 3 will fail:
>
> # hcitool scan -i hci1
> Scanning...
>
> Inquiry failed. Connection timed out.
> #
> #
>
> The test works fine if I do NOT use hcidump. That is, I can run window
> 1 and 3 all day with no problem. When I add hcidump, the "hcitool scan
> -i hci1" will then begin to fail to connect to the hci device.
Does using "hcitool inq" helps?
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-28 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 14:04 [Bluez-devel] hcidump with multiple dongles Williams, Richard
2007-06-28 14:57 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-28 14:06 Williams, Richard
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=1183042655.9499.22.camel@aeonflux.holtmann.net \
--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