From: Andreas Faerber <afaerber@rumms.uni-mannheim.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT
Date: Thu, 23 Mar 2006 14:05:14 +0100 [thread overview]
Message-ID: <44229D0A.5080508@rumms.uni-mannheim.de> (raw)
Hello,
We've just received an HCI 2.0 dongle (Belkin/Broadcom) and I've
recompiled my periodic scan code (on SuSE 10.1b8 w/BlueZ 2.24) to enable
support for EVT_EXTENDED_INQUIRY_RESULT. Unfortunately I still get the
"old" EVT_INQUIRY_RESULT only; I could not find an
OCF_EXTENDED_PERIODIC_INQUIRY command or the like so my expectation was
to simply get back EVT_EXTENDED_INQUIRY_RESULT from OCF_PERIODIC_INQUIRY
now that our hardware supports it (and I include it in the filter).
Am I missing anything? Do I need to enable this feature somewhere?
We want either EVT_INQUIRY_RESULT_WITH_RSSI or
EVT_EXTENDED_INQUIRY_RESULT because we need to read the RSSI without
connecting.
Regards,
Andreas
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-03-23 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 13:05 Andreas Faerber [this message]
2006-03-23 13:54 ` [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT Marcel Holtmann
2006-03-23 15:54 ` Andreas Faerber
2006-03-24 16:45 ` Marcel Holtmann
2006-03-24 17:35 ` Andreas Färber
2006-03-24 18:09 ` Marcel Holtmann
2006-03-24 19:18 ` Martin Karger
2006-04-13 16:25 ` [Bluez-devel] Periodic inquiry issues [was: EVT_EXTENDED_INQUIRY_RESULT] Andreas Faerber
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=44229D0A.5080508@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 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.