From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] multiple connection problem
Date: Fri, 17 Feb 2006 18:41:45 +0100 [thread overview]
Message-ID: <1140198105.4850.44.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <3ac394050602160549v2e7b7ebds2690192c067e3b2c@mail.gmail.com>
Hi Irfan,
> Thank you for ur feed back and help. I had stated in my previous mail
> that these dongles are working fine with other bluez
> functions/commands, but gives an error when a unit becomes slave of
> multiple masters. So is it just because of the hardware or it has some
> other reasons as well?
it is basically a limitation of the hardware. BlueZ has no limitations
in these area.
> Secondly I had a question about piconets. As slaves in piconet cannot
> directly communicate with each other and the master will act as a
> bridge for their communication. Now is this bridging facility provided
> by bluez libs? or do we have to implement it in our program (using
> Berkley Socket Interface) meant for piconet communication?
No. You have to implement this by yourself.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-17 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 13:49 [Bluez-devel] multiple connection problem Irfan Ahmad
2006-02-17 17:41 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-15 19:27 Irfan Ahmad
2006-02-15 19:31 ` Marcel Holtmann
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=1140198105.4850.44.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).