From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Jouni Malinen" <j@w1.fi>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>
Subject: scheduled scan api
Date: Wed, 7 May 2014 13:57:29 +0200 [thread overview]
Message-ID: <536A1FA9.7010404@broadcom.com> (raw)
Hi Johannes,
I received a couple of reports from people who got problem with brcmfmac
when a scheduled scan is requested, without any ssid specified.
Currently, brcmfmac basically rejects the request. So what are valid
usage scenarios for scheduled scans with respect to the n_ssid,
n_channels, and n_matchsets. In the kernel doc below it says a
zero-length ssid means 'no match'. I suppose it means any ssid which
signal is above RRSI threshold will match.
Regards,
Arend
---8<----------------------------------------------------------
/**
* struct cfg80211_match_set - sets of attributes to match
*
* @ssid: SSID to be matched; may be zero-length for no match (RSSI only)
* @rssi_thold: don't report scan results below this threshold (in s32 dBm)
*/
next reply other threads:[~2014-05-07 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 11:57 Arend van Spriel [this message]
2014-05-26 11:54 ` scheduled scan api Luca Coelho
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=536A1FA9.7010404@broadcom.com \
--to=arend@broadcom.com \
--cc=hostap@lists.shmoo.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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).