From: "Brian J. Murrell" <brian@whamcloud.com>
To: linux-bluetooth@vger.kernel.org
Cc: Brad Midgley <bmidgley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: how to set adapter to master with bluez 4.69?
Date: Thu, 17 Mar 2011 09:10:41 -0400 [thread overview]
Message-ID: <4D820851.4040809@interlinx.bc.ca> (raw)
In-Reply-To: <AANLkTim2oLMjE-9C0G7VCjXafg03xnb7a0Q04zwKh2ns@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]
On 11-03-15 11:25 AM, Brad Midgley wrote:
> Brian,
Hi Brad,
> You can have both master and slave connections simultaneously, just
> like you can be slave to more than one master. In both cases it means
> your adapter is in different piconets.
Ahhh. See. Shows what I know about the details of B/T. I thought one
adapter == one piconet.
> There are rules about whether devices can refuse the master/slave
> switch. It's been some time since I read this so I can't remember, but
> maybe it's the initiating device that starts out as slave and the
> remote device has to agree to a role switch.
Hrm. I guess I will have to play with that a bit.
> So you should be able to
> force the headset to cooperate, even if it's refusing role switches,
> by changing who initiates that connection in addition to a link policy
> that keeps your adapter as master.
OK. So as far as the link policy that keeps the adapter as master,
after having rebooted this machine today I found the following:
$ hcitool con
Connections:
$ hciconfig hci0 lm
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:1E:E0:12 ACL MTU: 1021:7 SCO MTU: 64:1
Link mode: SLAVE ACCEPT
So that means that the adapter will want to be the slave in all
connections, is that right?
I should change the above slave to master as such:
$ sudo hciconfig hci0 lm master
$ hciconfig hci0 lm
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:1E:E0:12 ACL MTU: 1021:7 SCO MTU: 64:1
Link mode: MASTER
Is that correct? Do I want to enable that "ACCEPT" also?
Once I do that, for my mouse at least, do I want to press the "Connect"
button on the mouse or use the Connect option for the mouse in the
bluetooth-applet?
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-03-17 13:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 2:07 how to set adapter to master with bluez 4.69? Brian J. Murrell
2011-03-06 22:28 ` Brian J. Murrell
2011-03-07 1:08 ` Brad Midgley
2011-03-07 21:13 ` Brian J. Murrell
2011-03-07 22:57 ` Andrei Warkentin
2011-03-08 11:08 ` Brian J. Murrell
2011-03-09 11:22 ` Brian J. Murrell
2011-03-07 23:09 ` Brad Midgley
2011-03-14 3:46 ` Brad Midgley
2011-03-14 11:00 ` Brian J. Murrell
2011-03-14 12:29 ` Brian J. Murrell
2011-03-14 14:07 ` Brian J. Murrell
2011-03-14 15:29 ` Brad Midgley
2011-03-15 0:23 ` Brian J. Murrell
2011-03-15 12:26 ` Brian J. Murrell
2011-03-15 12:43 ` Brian J. Murrell
2011-03-15 15:25 ` Brad Midgley
2011-03-17 13:10 ` Brian J. Murrell [this message]
2011-03-17 13:22 ` Brian J. Murrell
2011-03-17 15:46 ` Brad Midgley
2011-03-23 11:43 ` Brian J. Murrell
2011-03-23 12:20 ` Brian J. Murrell
2011-03-23 16:24 ` Brad Midgley
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=4D820851.4040809@interlinx.bc.ca \
--to=brian@whamcloud.com \
--cc=bmidgley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).