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 16:08:44 +0100	[thread overview]
Message-ID: <1133968124.3752.35.camel@blade> (raw)
In-Reply-To: <4396F911.40705@rumms.uni-mannheim.de>

Hi Andreas,

> We are trying to programmatically read the signal strength of Bluetooth 
> devices at discovery time (not only for connections). Seeing through the 
> source code it appears that in some cases (BT 1.2?) an inquiry gets an 
> HCI response that includes the RSSI (struct inquiry_info_with_rssi). 
> This information appears to be cached in struct inquiry_data if 
> available, 0 otherwise. However the only way to access this information 
> seems to be to get a pointer to a hci_dev struct (e.g. through 
> hci_dev_get(int index)) and use its inq_cache member? Getting this 
> information from the client side is not possible right now?
> 
> As I understand it from the code, the libBluetooth.so library does an 
> ioctl on an HCI socket with specific predefined commands such as HCIINQUIRY.
> How should we go about adding the functionality we need? Would we need 
> to define a custom HCI socket command and handle it somewhere in a 
> customized Kernel module? Or is there an easier way?

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.

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 15:08 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 [this message]
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
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=1133968124.3752.35.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).