From: "Andreas Färber" <afaerber@rumms.uni-mannheim.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Reading RSSI of non-connected devices
Date: Wed, 14 Dec 2005 21:43:13 +0100 [thread overview]
Message-ID: <43A083E1.1050804@rumms.uni-mannheim.de> (raw)
In-Reply-To: <1134580410.10473.5.camel@localhost>
Hi Marcel,
>>>>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.
>>>
>>>
>>>
>>For the two I mentioned it is not, there is none defined for the latter.
>>Only its size is - in bluez-libs-2.22.tar.gz.
>>But what about practical availability of those? When do we get which
>>response? Do you have any link on that or a short answer?
>>
>>
>
>look again, because they are different and bluez-libs-2.22 even contains
>the definitions for extended inquiry already.
>
>
No, all I was saying is that there was definately no
EVT_INQUIRY_RESULT_WITH_RSSI_AND_PSCAN_MODE defined in the
bluez-libs-2.22.tar.gz hci.h file, at least not anywhere near the
inquiry_info_with_rssi_and_pscan_mode struct. The extended_inquiry_info
struct on the other hand I even mentioned in the above quote, so I did
see it.
So you are saying that (theoretically) I should be able to distinguish
all responses by event code. In that case my question on when do I get
the respective event codes for an inquiry_info_with_rssi vs.
inquiry_info_with_rssi_and_pscan_mode vs. extended_inquiry_info still
stands...
Kind regards,
Andreas
-------------------------------------------------------
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 20: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
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 [this message]
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=43A083E1.1050804@rumms.uni-mannheim.de \
--to=afaerber@rumms.uni-mannheim.de \
--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).