From: Pedro Monjo Florit <pedro.monjo@futurlink.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Multiple Bluetooth connections
Date: Wed, 16 Mar 2005 12:23:31 +0100 [thread overview]
Message-ID: <42381733.50901@futurlink.com> (raw)
In-Reply-To: <1110966130.9818.95.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
Hi Marcel,
>this is a hardware limit and I don't know of any chip that is capable of
>establishing two connections at the same time. From what I know this
>will never be possible, but you should better ask a radio/baseband
>expert for a correct answer.
>
Thank you for the information. Together with the post of Peter
Stephenson (thank you, Peter), it seems that this problem cannot be
circumvented as I want to connect to different devices (as I understand,
various ACL connections; is this right?). I will have to live with it. :-(
>>On the other hand, some connections die before sending the data, but it
>>seems that the file descriptor of this connection does not receive any
>>notification (I use select() on all file descriptors, with the file
>>descriptor in the read mask). I know that this could be due to a problem
>>with my program, a problem with OpenOBEX or the BlueZ version I am using
>>(it is not the latest). In any case, to track down the cause, I would
>>like to know how can I monitor the Bluetooth connections (at any level,
>>but preferably RFCOMM) that a process (or the whole system) has. What I
>>am looking for is a tool like netstat.
>>
>
>Using poll() or select() is the right way. About what version of the
>kernel and library/utils are we talking?
>
I am using SuSE 9.1 with the latest updates from SuSE: kernel
2.6.5-7.147-default, bluez-libs 2.5-43 and bluez-utils 2.4-65. I know
they are old, so it could perfectly be a problem with them; therefore I
am planning an upgrade, but I am not quite sure whether I will be able
to use the latest BlueZ upgrades. The problem with the lost established
connections does not happen always, so I still have to look exactly why
this happens. In any case, besides that, everything else works as
expected. The only thing I am missing is a tool like "netstat" for
Internet an Unix sockets. "lsof" does not give any information either.
Is there anything of the like for BlueZ?
In any, case, thanks for the help.
Pedro
[-- Attachment #2: Type: text/html, Size: 2545 bytes --]
next prev parent reply other threads:[~2005-03-16 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 18:48 [Bluez-users] Multiple Bluetooth connections Pedro Monjo Florit
2005-03-15 19:27 ` sir
2005-03-16 9:42 ` Marcel Holtmann
2005-03-16 10:40 ` Peter Stephenson
2005-03-16 11:23 ` Pedro Monjo Florit [this message]
2005-03-16 11:44 ` Marcel Holtmann
[not found] ` <marcel@holtmann.org>
2018-10-30 10:24 ` [PATCH v2] Bluetooth: Support fast advertising interval Bharat Bhusan Panda
2018-11-13 9:00 ` Panda, Bharat B
2018-11-23 10:52 ` Panda, Bharat B
2018-12-07 12:34 ` Panda, Bharat B
2018-12-18 23:30 ` Marcel Holtmann
2019-02-04 9:10 ` Panda, Bharat B
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=42381733.50901@futurlink.com \
--to=pedro.monjo@futurlink.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 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.