From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Vasily Ulyanov <vulyanov@quantenna.com>
Subject: Re: [RFC PATCH 2/2] nl80211: implement beacon change notifier
Date: Mon, 13 Nov 2017 15:00:55 +0300 [thread overview]
Message-ID: <20171113115841.3dcrcjqnp543kndi@bars> (raw)
In-Reply-To: <1510565429.30497.10.camel@sipsolutions.net>
Hello Johannes and all,
> > From: Vasily Ulyanov <vulyanov@quantenna.com>
> >
> > Notify user-space listeners about beacon data change.
>
> What would this be needed for, and why couldn't you just directly talk
> to hostapd/wpa_s?
I apologize for email duplication, but it looks like reply from Vasily
has been rejected due to Outlook issues. While we choose between mutt
and gnus, here I briefly repeat the rationale behind these RFC patches.
The nl80211 get_beacon callback appears to be useful in the case when
userspace software needs to retrieve current operational parameters of
AP including HT/VHT IEs. In fact we considered two implementation options:
to implement this functionality either in hostapd (extending its
hostapd_cli interface) or in kernel (adding nl80211 call).
We decided to try nl80211 since there was a stub for NL80211_CMD_GET_BEACON
operation. Beacon change notifier was introduced due to the following reason:
if anyone is interested in AP operational params, then he might be also
interested to know when those params are changed.
Regards,
Sergey
next prev parent reply other threads:[~2017-11-13 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:40 [RFC PATCH 1/2] nl80211: implement NL80211_CMD_GET_BEACON command Sergey Matyukevich
2017-11-09 9:40 ` [RFC PATCH 2/2] nl80211: implement beacon change notifier Sergey Matyukevich
2017-11-13 9:30 ` Johannes Berg
2017-11-13 12:00 ` Sergey Matyukevich [this message]
2017-11-13 12:22 ` Johannes Berg
2017-11-15 15:35 ` Sergey Matyukevich
2017-11-27 12:02 ` Johannes Berg
2017-12-05 20:31 ` Sergey Matyukevich
2017-12-19 17:00 ` 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=20171113115841.3dcrcjqnp543kndi@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=avinashp@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vulyanov@quantenna.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox