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>,
Marianna Carrera <mcarrera@quantenna.com>
Subject: Re: [RFC PATCH 2/2] nl80211: implement beacon change notifier
Date: Wed, 15 Nov 2017 18:35:49 +0300 [thread overview]
Message-ID: <20171115153547.kkunkrfcivoqcsq2@bars> (raw)
In-Reply-To: <1510575765.30497.38.camel@sipsolutions.net>
Hello Johannes,
> > 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.
>
> Do you have any usage in mind though? I can't really see where this
> would really make sense, rather than getting direct hooks for the bits
> you needed in hostapd.
>
> For example, if you care about the channel bandwidth changing, wouldn't
> it be more efficient to just add a signal to hostapd rather than
> listening to beacon updates and parsing, etc.?
In our case, we are experimenting with applications running along with
hostapd and enabling band steering and client roaming functionality.
As I mentioned, various approaches are being examined, including
both pure nl80211-based approach as well as adding direct hooks
to hostapd.
Regards,
Sergey
next prev parent reply other threads:[~2017-11-15 15:35 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
2017-11-13 12:22 ` Johannes Berg
2017-11-15 15:35 ` Sergey Matyukevich [this message]
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=20171115153547.kkunkrfcivoqcsq2@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=mcarrera@quantenna.com \
--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