From: Johannes Berg <johannes@sipsolutions.net>
To: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH 0/3] Add support for ftm responder configuration
Date: Wed, 22 Aug 2018 09:27:36 +0200 [thread overview]
Message-ID: <1534922856.25523.60.camel@sipsolutions.net> (raw)
In-Reply-To: <7999c366492a4523456227fb49329bf2@codeaurora.org>
On Tue, 2018-08-21 at 15:08 -0700, Pradeep Kumar Chitrapu wrote:
> > Right. However, I guess we could allow updating/changing this setting
> > on
> > the fly through nl80211_set_beacon() which already allows changing
> > other
> > non-beacon parameters (like the probe or assoc response templates), and
> > then we can use your approach. Basically changing "SET_BEACON" to be a
> > bit like "CHANGE_AP".
>
> Agree. ( ftm_responder param will have to be added in
> cfg80211_beacon_data
> instead of cfg80211_ap_settings)
Right. I'm not even sure that all devices can disable it though, so we
may be in a bind here? I think ours (Intel) can't, for example, disable
FTM responder without disabling the AP (at least momentarily)...
Should we just ignore that? Or perhaps add a separate capability for it?
Maybe there's even hardware that cannot change the elements (LCI/Civic
location) on the fly?
johannes
next prev parent reply other threads:[~2018-08-22 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 22:08 [PATCH 0/3] Add support for ftm responder configuration Pradeep Kumar Chitrapu
2018-08-22 7:27 ` Johannes Berg [this message]
2018-08-22 18:22 ` Pradeep Kumar Chitrapu
2018-08-28 8:43 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2018-08-15 0:30 Pradeep Kumar Chitrapu
2018-08-15 9:04 ` Johannes Berg
2018-08-16 1:50 ` pradeepc
2018-08-16 8:12 ` Johannes Berg
2018-08-18 7:50 ` Pradeep Kumar Chitrapu
2018-08-20 9:33 ` Johannes Berg
2018-08-21 18:32 ` Pradeep Kumar Chitrapu
2018-08-21 19:24 ` Johannes Berg
2018-08-16 9:21 ` Kalle Valo
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=1534922856.25523.60.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeepc@codeaurora.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).