From: George Hansel <ghansel@MIT.EDU>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Handling simultaneous SCO connections: Does BlueZ have multiple SCO buffers?
Date: Wed, 11 Jul 2007 14:30:00 -0400 [thread overview]
Message-ID: <1184178600.6062.27.camel@Epimenides> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1748 bytes --]
I'm working on a project which is trying to handle multiple SCO
connections and data transfer (from cell phones) simultaneously, whether
that involves using multiple Bluetooth adapters on a single computer
(one SCO connection per adapter) or multiple connections per adapter (up
to the maximum of 3).
I have a process which handles the initial RFCOMM setup, the AT commands
involved in having the computer pretend to be a Hands-Free Device, and
accepts an SCO connection once the phone initiates. It's written in
Python using the PyBlueZ module. Multiple processes are launched in
order to handle multiple connections, and I've so far been able to
establish multiple RFCOMM connections on a single and on multiple
adapters.
The problem arises when I try to start multiple SCO connections (by
pressing buttons on the cell phone, so as to send DTMF tones over the
connection). I am not able to establish multiple simultaneous SCO
connections, and not only that, but the SCO data is directed to a
different process every time the SCO connection resets (due to 3 seconds
of silence - this is a feature of the Hands-Free Profile). This makes it
seem as though there is only one SCO buffer somewhere in the stack, and
any waiting process just reads from it, assuming that it's the proper
data.
My question: Is it true that BlueZ has only one buffer for SCO data? If
this is true, where in the BlueZ stack is this single implementation (in
the kernel drivers? in the bluez-libs? in the bluez-utils?)? I'd have no
reservations about trying to implement a second (or third, as the
protocol truly demands) one. Lastly, if this is not a BlueZ problem at
all, but rather a hardware or PyBlueZ issue, just let me know.
Thanks for any consideration,
George
[-- Attachment #1.2: Type: text/html, Size: 2013 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-07-11 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 18:30 George Hansel [this message]
2007-07-11 20:02 ` [Bluez-devel] Handling simultaneous SCO connections: Does BlueZ have multiple SCO buffers? Brad Midgley
2007-07-12 4:58 ` [Bluez-devel] Handling simultaneous SCO connections: Does BlueZhave " Niels v/d Spek
2007-07-12 8:01 ` George Hansel
2007-07-12 9:27 ` Alok
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=1184178600.6062.27.camel@Epimenides \
--to=ghansel@mit.edu \
--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