From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Troubles with mulitple SCO connections (duplex)
Date: Wed, 04 Apr 2007 08:06:11 -0600 [thread overview]
Message-ID: <4613B0D3.8010706@xmission.com> (raw)
In-Reply-To: <4613AC43.8090500@free2move.net>
Markus
> My spontaneous reaction would be; really?
>
> My code is based on the socket-abstraction in BlueZ and it works fine
> for multiple ACL connections
Marcel says the usb layer needs a rewrite to accommodate this. It has
something to do with resource allocation on usb iirc.
It does work now on systems that use a serial hci connection (mostly
embedded) but that may not help you.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-04 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 8:24 [Bluez-devel] Troubles with mulitple SCO connections (duplex) Markus Adolfsson
2007-04-04 11:40 ` Jose Vasconcellos
2007-04-04 13:46 ` Markus Adolfsson
2007-04-04 14:06 ` Brad Midgley [this message]
2007-04-04 14:32 ` Markus Adolfsson
2007-04-11 8:16 ` Markus Adolfsson
2007-04-11 8:21 ` Mayank BATRA
2007-04-11 8:36 ` Markus Adolfsson
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=4613B0D3.8010706@xmission.com \
--to=bmidgley@xmission.com \
--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