From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] How to bypass inquiry cache?
Date: Mon, 30 Jul 2007 20:57:12 +0200 [thread overview]
Message-ID: <1185821832.5868.142.camel@violet> (raw)
In-Reply-To: <0537279F-C314-4CED-A04C-28B306778F87@pi4.informatik.uni-mannheim.de>
Hi Andreas,
> How can I perform non-standard inquiries without caching?
>
> I am using an HCI socket to start my inquiry but the results somehow
> appear to be cached - i.e. the RSSI doesn't change although it
> should, but does after I re-plug the dongle.
>
> We tried setting the two maximum cache age defines in hci_core.c to
> zero but this made the whole inquiry run forever apparently.
>
> Where in the kernel code is such caching handled? I only found the
> cache maintenance functions and inquiry ioctl handling in hci_core.*,
> the cache updating in hci_event.c and one other reference to the
> cache limit in hci_conn.c - neither of those appeared to override the
> value returned to userland so I must've missed something...
simply use the D-Bus API for scanning. It does all you want.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-30 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 16:49 [Bluez-devel] How to bypass inquiry cache? Andreas Färber
2007-07-30 18:57 ` Marcel Holtmann [this message]
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=1185821832.5868.142.camel@violet \
--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