From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jakub Pawlowski <jpawlowski@google.com>
Cc: Arman Uguray <armansito@chromium.org>,
Marcel Holtmann <marcel@holtmann.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Scott James Remnant <keybuk@google.com>
Subject: Re: [RFC] need for new scan api for bluetooth low energy.
Date: Wed, 17 Sep 2014 10:31:20 +0300 [thread overview]
Message-ID: <20140917073120.GB7640@t440s.lan> (raw)
In-Reply-To: <CAD0=r8z9g+F7Z9X_8PE4jk3JbA+oLj9Of33RSqxiRd0dn9AnXQ@mail.gmail.com>
Hi Jakub,
On Wed, Sep 17, 2014, Jakub Pawlowski wrote:
> >> My use case include scanning for non-paired, non-connected devices,
> >> checking RSSI value and deciding about connection based on
> >> advertisement content, so that won't work. Am I right ?
> >
> > If you know the bdaddr that you're interested in in advance we should be
> > able to tweak the Add Device command to do what you want (e.g. disable
> > duplicate filtering in the case of Action=0x00 entries). However, if
> > what you need is general scanning for any devices (also previously
> > unknown ones) then Add Device doesn't really fit in (since it takes a
> > known bdaddr). For that we'd either need to consider allowing BDADDR_ANY
> > as an accepted parameter or then we'd need to define a new mgmt command.
> >
>
> Unfortunately my case include previously unknown devices. I decide
> wether I should connect (without pairing) based on advertised service
> and RSSI power only. BDADDR_ANY seems good solution. Or maybe we can
> add some parameter that will force not using controller-side whitelist
> for scan?
With the BDADDR_ANY solution that'd be the trigger not to use the
controller-side white list. Simply disabling the controller side white
list isn't enough since the kernel would still filter out unknown
addresses and never send Device Found mgmt events.
Johan
next prev parent reply other threads:[~2014-09-17 7:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 3:30 [RFC] need for new scan api for bluetooth low energy Jakub Pawlowski
2014-09-17 4:39 ` Marcel Holtmann
2014-09-17 4:52 ` Arman Uguray
2014-09-17 5:14 ` Johan Hedberg
2014-09-17 6:20 ` Jakub Pawlowski
2014-09-17 6:52 ` Johan Hedberg
2014-09-17 7:19 ` Jakub Pawlowski
2014-09-17 7:31 ` Johan Hedberg [this message]
2014-09-17 7:44 ` Johan Hedberg
2014-09-17 14:03 ` Marcel Holtmann
2014-09-18 5:58 ` Jakub Pawlowski
2014-09-18 15:37 ` Marcel Holtmann
2014-09-19 16:39 ` Jakub Pawlowski
2014-09-19 16:44 ` Jakub Pawlowski
2014-09-20 1:43 ` Marcel Holtmann
[not found] ` <F673E928-258E-47F7-B71A-F32410974538@holtmann.org>
2014-09-20 4:29 ` Jakub Pawlowski
2014-09-30 16:44 ` Jakub Pawlowski
2014-09-30 17:01 ` Marcel Holtmann
2014-09-30 17:15 ` Arman Uguray
2014-09-30 17:24 ` Marcel Holtmann
2014-09-30 17:25 ` Jakub Pawlowski
2014-09-30 17:31 ` Marcel Holtmann
2014-09-30 18:29 ` Jakub Pawlowski
2014-09-30 18:54 ` Marcel Holtmann
2014-09-30 21:11 ` Jakub Pawlowski
2014-10-01 5:27 ` Marcel Holtmann
2014-10-10 10:52 ` Marcel Holtmann
2014-10-10 15:49 ` Jakub Pawlowski
2014-10-20 16:55 ` Jakub Pawlowski
2014-10-20 18:22 ` 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=20140917073120.GB7640@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=armansito@chromium.org \
--cc=jpawlowski@google.com \
--cc=keybuk@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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