From: "Olivier Le Pogam" <olepogam@free.fr>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Master / Slave question
Date: Tue, 28 Nov 2006 12:01:29 +0100 [thread overview]
Message-ID: <000701c712dc$8e44ff20$3978f052@kayleigh> (raw)
In-Reply-To: Pine.LNX.4.63.0611281118300.29749@redbean.intranet.gw-instruments.de
Hi Peter,
Many many many thanks for your answer, I was supposing
a low level issue indeed !
I am actually using a generic Bluetooth key, the kind of
ones you can plug everywhere and which are recognised
by Microsoft Drivers. It is a HCI type 1 (Bluetooth 1.1).
So basically ... only 1 slave connection at a time for
each bluetooth adaptor ? How many bluetooth adaptors
do you think I can deal with under BlueZ in the case I
definetely want to be able to deal with concurrent incoming
connections ?
Even if I buy bluetooth 2.0 adaptors, I suppose the problem
will be the same, assuming my mobile phones are anyway
always on a lower bluetooth version ?
Many thanks again,
Oli
----- Original Message -----
From: "Peter Wippich" <pewi@gw-instruments.de>
To: "Olivier Le Pogam" <olepogam@free.fr>; "BlueZ development"
<bluez-devel@lists.sourceforge.net>
Sent: Tuesday, November 28, 2006 11:24 AM
Subject: Re: [Bluez-devel] Master / Slave question
>
> Hi Olivier,
>
>>> lots of stuff deleted.....
>
> your problem is hardware / general Bluetooth / LM related.
>
> Earlier BT implementations (and may be even actual) support only one slave
> connection at a time. This is why the master slave switch was introduced !
> (I think with BT 1.0B).
> Newer implementations MAY support up to two slave connections or at least
> one Master and one Slave connection.
>
> What hardware are you using ?
>
> Ciao,
>
> Peter
>
>
>
> | Peter Wippich Voice: +49 30 46776411 |
> | G&W Instruments GmbH fax: +49 30 46776419 |
> | Gustav-Meyer-Allee 25, Geb. 12 Email: pewi@gw-instruments.de |
> | D-13355 Berlin / Germany |
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.14.19/555 - Release Date:
> 27/11/2006
>
>
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.19/555 - Release Date: 27/11/2006
-------------------------------------------------------------------------
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:[~2006-11-28 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 15:40 [Bluez-devel] Master / Slave question Olivier Le Pogam
2006-11-26 10:13 ` Marcel Holtmann
2006-11-27 20:05 ` Olivier Le Pogam
2006-11-28 10:24 ` Peter Wippich
2006-11-28 11:01 ` Olivier Le Pogam [this message]
2006-11-28 11:34 ` Peter Wippich
2006-11-28 12:32 ` Olivier Le Pogam
2006-11-29 12:11 ` Peter Wippich
2006-11-29 22:54 ` Mark S. Townsley
2006-11-30 17:12 ` Andrew Kohlsmith
2006-12-01 13:22 ` Peter Wippich
2006-12-01 15:33 ` Andrew Kohlsmith
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='000701c712dc$8e44ff20$3978f052@kayleigh' \
--to=olepogam@free.fr \
--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