From: Aloka Dixit <alokad@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/2] nl80211: Unsolicited broadcast probe response support
Date: Mon, 03 Aug 2020 10:33:45 -0700 [thread overview]
Message-ID: <352e032b1b9086df89aa8ba862c5a91f@codeaurora.org> (raw)
In-Reply-To: <df36ecfb6fd72531727a0322f060a57761985294.camel@sipsolutions.net>
On 2020-08-03 03:20, Johannes Berg wrote:
> On Wed, 2020-07-15 at 16:05 -0700, Aloka Dixit wrote:
>> This patch adds new attributes to support unsolicited broadcast
>> probe response transmission used for in-band
>> discovery in 6GHz band (IEEE P802.11ax/D6.0 26.17.2.3.2, AP behavior
>> for
>> fast passive scanning).
>> The new attribute, NL80211_ATTR_UNSOL_BCAST_PROBE_RESP, is nested
>> which
>> supports following parameters:
>> (1) NL80211_UNSOL_BCAST_PROBE_RESP_INT - Packet interval
>> (2) NL80211_UNSOL_BCAST_PROBE_RESP_TMPL - Template data
>
> And maybe some driver support flag is needed?
>
> johannes
Are you referring to enable/disable flag separate from the interval
field being used for that? Or a different command/event from driver to
netlink advertising if the driver supports this feature?
If former, it isn't needed because interval=0 means disable.
Thanks.
next prev parent reply other threads:[~2020-08-03 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 23:05 [PATCH v3 0/2] Unsolicited broadcast probe resp support Aloka Dixit
2020-07-15 23:05 ` [PATCH v3 1/2] nl80211: Unsolicited broadcast probe response support Aloka Dixit
2020-08-03 10:18 ` Johannes Berg
2020-08-03 17:28 ` Aloka Dixit
2020-08-03 10:20 ` Johannes Berg
2020-08-03 17:30 ` Aloka Dixit
2020-08-03 10:20 ` Johannes Berg
2020-08-03 10:21 ` Johannes Berg
2020-08-03 17:33 ` Aloka Dixit [this message]
2020-07-15 23:05 ` [PATCH v3 2/2] mac80211: " Aloka Dixit
2020-07-16 9:35 ` [PATCH v3 0/2] Unsolicited broadcast probe resp support Arend Van Spriel
2020-07-20 21:36 ` Aloka Dixit
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=352e032b1b9086df89aa8ba862c5a91f@codeaurora.org \
--to=alokad@codeaurora.org \
--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).