From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Reading RSSI of non-connected devices
Date: Wed, 14 Dec 2005 17:23:42 +0100 [thread overview]
Message-ID: <1134577422.10473.1.camel@localhost> (raw)
In-Reply-To: <43A03888.5010105@rumms.uni-mannheim.de>
Hi Andreas,
> I've made some progress on our periodic scan test code. I didn't find
> the example you referenced but I have managed to initiate a periodic
> scan, to read some events and to stop the scan. Some things I noticed
> however, for instance that when I ran my app twice a little time-shifted
> the second process didn't get any events once the first process was
> finished. Can I avoid this somehow? Currently I am catching the
> EVT_CMD_COMPLETE event for OCF_EXIT_PERIODIC_INQUIRY and restarting the
> search, but as I am not getting an event for the start of the periodic
> inquiry that I could process it would seem that if I do e.g. a 3 second
> period inquiry and during my scan afterwards someone else does e.g. a 30
> second period inquiry then it will change this on a global level so that
> I do not get my results as expected?
you don't need to stop the periodic inquiry. It will restart itself.
That's the whole point behind it.
> Regarding the multitude of events, how do I distinguish between the
> inquiry_info_with_rssi and inquiry_info_with_rssi_and_pscan_mode
> structs? They appear to be using the same event but would be
> incompatible due to the "inserted" pscan_mode member. Currently I am
> testing with an HCI 1.1 device and getting only the inquiry_info struct.
> Which of the other inquiry+RSSI events map to which HCI version? Is
> inquiry_info_with_rssi HCI 1.2 and extended_inquiry_info HCI 2.0? Or do
> these responses depend on anything else?
The event code is different.
> Oh, and is it not possible to send HCI commands as a non-root user? We
> were getting EPERM from hci_send_cmd and had to setup a Linux box solely
> for this purpose so that I could be root - admins wouldn't allow that on
> the other University machines, and I'm concerned whether our potential
> users would all be able to run our software as root...
The inquiry related commands and events are accessable by all users.
Some other are protected by the HCI security inside the kernel.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-14 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 15:00 [Bluez-devel] Reading RSSI of non-connected devices Andreas Färber
2005-12-07 15:08 ` Marcel Holtmann
2005-12-07 16:21 ` Andreas Färber
2005-12-07 16:43 ` Marcel Holtmann
2005-12-14 15:21 ` Andreas Faerber
2005-12-14 15:26 ` Bastien Nocera
2005-12-14 16:44 ` Andreas Faerber
2005-12-14 17:17 ` Marcel Holtmann
2005-12-14 20:53 ` Andreas Färber
2005-12-14 16:23 ` Marcel Holtmann [this message]
2005-12-14 16:58 ` Andreas Faerber
2005-12-14 17:13 ` Marcel Holtmann
2005-12-14 20:43 ` Andreas Färber
2005-12-15 5:15 ` 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=1134577422.10473.1.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).