linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Reading RSSI of non-connected devices
Date: Wed, 07 Dec 2005 17:43:03 +0100	[thread overview]
Message-ID: <1133973783.3752.47.camel@blade> (raw)
In-Reply-To: <43970C1E.6020602@rumms.uni-mannheim.de>

Hi Andreas,

> >the ioctl() is very old and number updated it to support Inquiry with
> >RSSI or Extended Inquiry. The main reason for this is, because you can't
> >update it without breaking backward-compatibility with older versions of
> >the library and the tools.
> >
> >However you can program the HCI socket interface directly and read the
> >inquiry result directly. Example code for this is already available in
> >the mailing list archives.
> >  
> >
> Some posts say ioctl was bad because it's old, some posts say raw HCI 
> sockets were bad because the messed with BlueZ. Your hcitool apparently 
> is using ioctl for "hcitool scan" in its most recent version 
> downloadable from your site...

you should avoid interfacing with the kernel, but listening for events
on the HCI socket was and will be always safe.

> Our software is a Java framework that shall continuously check the RSSI 
> of devices around in a background thread (test code for this is in C). 
> Another thread might be continuously using GPS data via BT and apart 
> from that we don't want to keep the user from using the BlueZ stack in a 
> "normal" way while our software is running. In this context is it safe 
> to use HCI sockets in the way you have suggested?

In this case you should use periodic inquiry and listen for inquiry
result events on the HCI raw socket. This is a safe way of doing it. You
might wanna check out the D-Bus interface, but this new API might be
still changed at lot.

> I'm having a hard time finding the example you're mentioning over and 
> over... Do you have any search words for me?
> Not having found it I would assume you mean hci_open_dev and 
> hci_send_cmd? Examples for the latter would be in the kernel driver 
> which I already have.

Try to look for EVT_INQUIRY_RESULT_WITH_RSSI.

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

  reply	other threads:[~2005-12-07 16:43 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 [this message]
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
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=1133973783.3752.47.camel@blade \
    --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).