From: Tamer Higazi <tamer23@myrealbox.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Belkin F8T009 and Linux
Date: Thu, 09 Feb 2006 06:49:08 +0000 [thread overview]
Message-ID: <1139467748.10136.2.camel@localhost> (raw)
In-Reply-To: <loom.20060209T033130-898@post.gmane.org>
Dear Heba!
Why don't you sniff the traffic by opening a 2nd shell, by writing:
hcidump -X -V
and post it in the news! Or try finding at bluez "docu" to find more
about the output, the shell would give you to analyze the problem at
all. The out put could tell much more...
Tamer
On Thu, 2006-02-09 at 02:48 +0000, Heba wrote:
> I am developing an application for automatic network discovery using bluetooth
> i.e. Running the application will result in connections to any other computers
> running the same application:
> - Each application is running a server which accepts connections (once a
> connection is made, the connection is maintained until a transmission
> error occcurs or the socket is closed by either party);
> - and a client which repeatedly queries for bluetooth devices to connect to.
>
> So in total an application makes and
> maintains 2*(#other applications) connections.
>
> This causes no problems when using the Belkin F8T003 Bluetooth USB Adaptor
> (this is a bluetooth v1.1 compliant device).
>
> However, when using the Belkin F8T009 Bluetooth USB Adaptor
> (this is a bluetooth v1.2 compliant device)
> "Device or Resource Busy" errors are observed
> when the application tries to query
> when there are 3 or more connections maintained by it.
>
> Is this a bluetooth hardware issue,
> a Bluez stack issue,
> or does Bluez just not support this particular device??
>
> I have installed all the latest versions:
> - Bluez-lib
> - Bluez-hcidump
> I am running Fedora core 4 with the latest available updates of the kernel.
>
> Please advise if I am overlooking something, or if this is not a Bluez issue,
> could you please direct me to the appropriate contact.
>
> Thanks
> Heba
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-09 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 2:48 [Bluez-users] Belkin F8T009 and Linux Heba
2006-02-09 6:49 ` Tamer Higazi [this message]
2006-02-12 23:23 ` FW: " Heba.Khamis
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=1139467748.10136.2.camel@localhost \
--to=tamer23@myrealbox.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;
as well as URLs for NNTP newsgroup(s).