Linux bluetooth development
 help / color / mirror / Atom feed
From: "Olivier Le Pogam" <olepogam@free.fr>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Master / Slave question
Date: Sat, 25 Nov 2006 16:40:34 +0100	[thread overview]
Message-ID: <002901c710a8$0eab3580$0100a8c0@kayleigh> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1149 bytes --]

Hi,

I am trying to make 2 mobile phones connected concurrently
to a RFCOMM server. Please note that they don't support
role switching, so as they initiate the communication, they
are always "master".

My RFCOMM server is a forking one so it can virtually
deal with concurrent clients like on TCP.

I have put lm=accept in hcid.conf

If I open a RFCOMM server on channel 14 and try to make
the 2 mobile connect to channel 14, the first is ok, the
second can't connect. I suppose that's normal, because
channel 14 "slave" is busy linux-side with the first
connection and a "slave" can deal with one connection only.

Then I've launched a second server on channel 15 (server
on channel 14 running concurrently), and i try to make
the first mobile connect to channel 14 and the second
to channel 15 : it's the same, only the first can connect.

I think I have a misunderstanding here, as i thought the
"master/slave" was per channel. Does it mean the "slave" status 
is for the whole adaptor, and once a "slave" connection is
open on one channel, it can't receive other connections at all ?

Thanks a lot for your help,
Oli

[-- Attachment #1.2: Type: text/html, Size: 2763 bytes --]

[-- Attachment #2: "AVG certification" --]
[-- Type: text/plain, Size: 151 bytes --]

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.15/550 - Release Date: 24/11/2006


[-- Attachment #3: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-11-25 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-25 15:40 Olivier Le Pogam [this message]
2006-11-26 10:13 ` [Bluez-devel] Master / Slave question 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
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='002901c710a8$0eab3580$0100a8c0@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