From: Pierre N <pierren@mac.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Two simultanous connections
Date: Sat, 03 Apr 2004 15:01:46 +0200 [thread overview]
Message-ID: <1080997306.12501.10.camel@localhost> (raw)
In-Reply-To: <1080994581.2839.26.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Sat, 2004-04-03 at 14:16, Marcel Holtmann wrote:
> Hi Pierre,
>
> > hcitool -a shows "invalid option -- a".
>
> who said that hcitool have an "-a" option.
Sorry, I mixed up hcitool and hciconfig...
> Actually I don't see your problem. Let one iPAQ be the master and the
> other connect as slaves.
Who said I had a problem? ;-p
This is all, as I said previously, out of curiosity...
Seriously, my question is why can a master hold up to 4 slaves but can't
initiate these 4 connections itself as a master?
Is it technically impossible, is it just an implementation constraint or
is there some secret switch to do so?
--
Pierre
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-03 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 18:00 [Bluez-users] Two simultanous connections Pierre N
2004-04-02 18:10 ` Marcel Holtmann
2004-04-03 11:50 ` Pierre N
2004-04-03 12:16 ` Marcel Holtmann
2004-04-03 13:01 ` Pierre N [this message]
2004-04-03 16:24 ` Andreas Gaufer
[not found] ` <20040403182354.5c3420eb.Andreas.Gaufer@blue-cell-networks.com>
2004-04-03 16:53 ` Pierre N
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=1080997306.12501.10.camel@localhost \
--to=pierren@mac.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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