From: Jouni Malinen <j@w1.fi>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] cfg80211: Allow a scan request for a specific BSSID
Date: Fri, 26 Feb 2016 20:27:06 +0200 [thread overview]
Message-ID: <20160226182706.GA22680@w1.fi> (raw)
In-Reply-To: <1456495566-14272-1-git-send-email-jouni@qca.qualcomm.com>
On Fri, Feb 26, 2016 at 04:06:04PM +0200, Jouni Malinen wrote:
> This allows scans for a specific BSSID to be optimized by the user space
> application by requesting the driver to set the Probe Request frame
> BSSID field (Address 3) to the specified BSSID instead of the wildcard
> BSSID. This prevents other APs from replying which reduces airtime need
> and latency in getting the response from the target AP through.
>
> This is an optimization and as such, it is acceptable for some of the
> drivers not to support the mechanism. If not supported, the wildcard
> BSSID will be used and more responses may be received.
> include/net/cfg80211.h | 2 ++
> include/uapi/linux/nl80211.h | 4 +++-
> net/wireless/nl80211.c | 6 ++++++
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> @@ -1471,6 +1472,7 @@ struct cfg80211_scan_request {
> + u8 bssid[ETH_ALEN] __aligned(2);
You should know better to run all hwsim test cases before sending
patches out.. nl80211 one is not enough when we have WEXT. :)
Johannes, please drop this. I'll need to talk to myself to get a fixed
version with the two other rdev_scan() callers updated to fill in the
bssid field.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2016-02-26 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 14:06 [PATCH 1/3] cfg80211: Allow a scan request for a specific BSSID Jouni Malinen
2016-02-26 14:06 ` [PATCH 2/3] mac80211: Support " Jouni Malinen
2016-02-26 14:06 ` [PATCH 3/3] mac80211_hwsim: Support a hw " Jouni Malinen
2016-02-26 18:27 ` Jouni Malinen [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=20160226182706.GA22680@w1.fi \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).