From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] rfcomm connect error Too many links(31)
Date: Wed, 18 Jan 2006 15:46:44 +0100 [thread overview]
Message-ID: <1137595604.4776.5.camel@localhost> (raw)
In-Reply-To: <20060118144029.GA60664@rucus.ru.ac.za>
Hi David,
> > but maybe not multiple ACL connections and this is what you need in your
> > case. So you need at least a CSR chip with HCI 18.x firmware or you
> > might wanna simply use another dongle. One for the incoming data and one
> > for the outgoing data.
>
> Thanks Marcel for the quick answer. Though you are the messenger with the
> bad news... It had not crossed my mind that this could be a problem. Do
> you know where I can find some reference to this online?
you can look at my page for the CSR chips and their firmware. Besides
this I don't think that you will find any further details. Use a second
dongle and this problem goes away.
Regards
Marcel
-------------------------------------------------------
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
prev parent reply other threads:[~2006-01-18 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 12:37 [Bluez-users] rfcomm connect error Too many links(31) David Mackie
2006-01-18 12:48 ` Marcel Holtmann
2006-01-18 14:40 ` David Mackie
2006-01-18 14:46 ` Marcel Holtmann [this message]
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=1137595604.4776.5.camel@localhost \
--to=marcel@holtmann.org \
--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).