From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] ioctl: setting link mode and link policy
Date: Thu, 31 Aug 2006 21:23:05 +0200 [thread overview]
Message-ID: <1157052185.4026.142.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <44F7115D.6080700@pracucci.com>
Hi Marco,
> >> I would like to set a "global" link mode and link policy that will be
> >> the default for every connection. Something similar to hcid.
> >>
> > what do you expect from doing this? It is not a good idea to change it
> > globally except you know exactly what you are doing. Changes these
> > settings can have implications you might not be aware of. So what is
> > your purpose on changing them?
> >
> I would become master on incoming connections and I would deny role
> switch on outgoing connections. If I'm not wrong, I should set MASTER as
> link mode and disable role switch from link policy.
this can't work. You must allow role switching. The initiator of a
piconet is always the master in the first place. They have to switch the
role to make the acceptor the master. So don't touch the link policy, it
must allow the role switch. Setting the link mode to MASTER will request
an immediate role switch after connection creation. However if both
sides have the MASTER link mode set, you will never get a connection,
because the initiator will refuse the switch the role.
> However, I can't use
> hcid, so I would do this from a custom application.
> Is it possible?
It is not wise at all to work without hcid. And you know that your
custom application must be placed under GPL.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-08-31 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:59 [Bluez-devel] ioctl: setting link mode and link policy Marco Pracucci
2006-08-31 12:18 ` Peter Wippich
2006-08-31 15:15 ` Marco Pracucci
2006-08-31 16:29 ` Marcel Holtmann
2006-08-31 16:42 ` Marco Pracucci
2006-08-31 19:23 ` Marcel Holtmann [this message]
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=1157052185.4026.142.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