From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] permissions to set local name
Date: Mon, 20 Nov 2006 09:43:24 +0100 [thread overview]
Message-ID: <1164012204.28397.22.camel@localhost> (raw)
In-Reply-To: <b5dccebe0611200031v64a8d2d0xfdd92edf29a44d0@mail.gmail.com>
Hi Mikael,
> How does hcid know what mode that is "best" for my application? I want
> to make sure that it is 1 (result with rssi), is there a way I can
> tell hcid to always choose that mode then?
if inquiry with RSSI is supported by the chip, it will be activated for
any bluez-utils-3.x you use. In case you already have a chip that
supports extended inquiry from the Bluetooth 2.1 specification, it will
also enable that by default.
The events that indicate that a new device has been found are send out
over D-Bus and they are unified between all versions of the Bluetooth
specification. That is internal to hcid and you applications don't have
to worry about this stuff anymore. Same goes for the name resolving
after the inquiry process. It is all taken care of.
> Also, I would like to have as few external dependencies, so if
> possible I would prefer to not use d-bus. Is there a way to set the
> local name without d-bus and without root privileges?
With the bluez-utils-3.x series, the D-Bus support is required. We don't
support any non D-Bus version anymore. You will see the long term
advantage of D-Bus once you start using it. Trust me. I wasn't a believe
for a long time, but nowadays, D-Bus is the way to go.
Anyway, there is a security filter inside the kernel that can be
modified to allows certain commands for non-root users. However you are
on you own with doing that.
Regards
Marcel
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-11-20 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:50 [Bluez-users] permissions to set local name Mikael Lindqvist
2006-11-19 12:47 ` Marcel Holtmann
2006-11-20 8:31 ` Mikael Lindqvist
2006-11-20 8:43 ` Marcel Holtmann [this message]
2006-11-21 9:14 ` Mikael Lindqvist
2006-11-21 9:17 ` Marcel Holtmann
2006-11-21 9:36 ` Mikael Lindqvist
2006-11-21 11:10 ` Marcel Holtmann
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=1164012204.28397.22.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.