From: Luca Coelho <luca@coelho.fi>
To: Johannes Berg <johannes@sipsolutions.net>,
Arend Van Spriel <arend.vanspriel@broadcom.com>,
Jouni Malinen <jouni@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, vamsi krishna <vamsin@qti.qualcomm.com>
Subject: Re: [PATCH 2/2] cfg80211: Add support to sched scan to report better BSSs
Date: Mon, 28 Nov 2016 16:34:06 +0200 [thread overview]
Message-ID: <1480343646.29540.20.camel@coelho.fi> (raw)
In-Reply-To: <1480342821.8107.44.camel@sipsolutions.net>
On Mon, 2016-11-28 at 15:20 +0100, Johannes Berg wrote:
> > It seems there has already
> > been taken a shot at this which may be used/extended [1].
> >
>
> That's a good point - it's somewhat similar.
>
> This is obviously a different context - offloaded BSS selection vs.
> scheduled scan (for host BSS selection), but perhaps the attribute &
> definitions could be reused?
Yes, similar but not quite the same. The existing case is for finding
BSSs that are worth waking the host up for (while disconnected), so it
needs to be better than the RSSI passed (absolute number). Now this is
about relative RSSI as compared to the current connection, so
RELATIVE_RSSI is different than RSSI and I think the same attribute
should not be used, to avoid confusion.
--
Luca.
next prev parent reply other threads:[~2016-11-28 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 22:07 [PATCH 1/2] nl80211: Use different attrs for BSSID and random MAC addr in scan req Jouni Malinen
2016-11-23 22:07 ` [PATCH 2/2] cfg80211: Add support to sched scan to report better BSSs Jouni Malinen
2016-11-25 9:21 ` Luca Coelho
2016-12-02 21:48 ` Malinen, Jouni
2016-11-27 20:51 ` Arend Van Spriel
2016-11-28 14:20 ` Johannes Berg
2016-11-28 14:34 ` Luca Coelho [this message]
2016-11-28 14:17 ` Johannes Berg
2016-11-25 8:44 ` [PATCH 1/2] nl80211: Use different attrs for BSSID and random MAC addr in scan req Luca Coelho
2016-11-28 14:14 ` Johannes Berg
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=1480343646.29540.20.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=arend.vanspriel@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vamsin@qti.qualcomm.com \
/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.