From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT
Date: Fri, 24 Mar 2006 17:45:50 +0100 [thread overview]
Message-ID: <1143218750.12582.33.camel@localhost> (raw)
In-Reply-To: <4422C49C.2060004@rumms.uni-mannheim.de>
Hi Andreas,
> >You can also check the features with "hciconfig hci0 features" if it
> >tells you it supports inquiry with RSSI. However in case of some
> >Broadcom chips, this doesn't mean anything, because they support it
> >anyway even if the features bit is not set.
> >
> The feature is actually listed. The only weird thing I'm still tracking
> down is that I only get inquiry results every five minutes while it did
> work as expected with the previous dongles...
ask Broadcom, I have no idea. You might wanna try to compare it against
a CSR based dongle.
Regards
Marcel
-------------------------------------------------------
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 prev parent reply other threads:[~2006-03-24 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 13:05 [Bluez-devel] EVT_EXTENDED_INQUIRY_RESULT Andreas Faerber
2006-03-23 13:54 ` Marcel Holtmann
2006-03-23 15:54 ` Andreas Faerber
2006-03-24 16:45 ` Marcel Holtmann [this message]
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=1143218750.12582.33.camel@localhost \
--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