From: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> To: Johannes Berg <johannes@sipsolutions.net> 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: Tue, 21 Aug 2018 15:08:02 -0700 [thread overview] Message-ID: <7999c366492a4523456227fb49329bf2@codeaurora.org> (raw) On 2018-08-21 12:24, Johannes Berg wrote: > On Tue, 2018-08-21 at 11:32 -0700, Pradeep Kumar Chitrapu wrote: >> >> I wasn't aware of this android api. > > OK. > >> However, looking at the api, the >> assumption is that bss is started by a different >> api and the 'enableResponder' api is used for enabling rtt for a given >> duration. > > It looks like. Note that there's also *disable*, which we hadn't even > implemented before. > >> The reason we have added enabling ftm responder through start ap is >> that >> this can reflect beacon IE change in the >> configuration in the same place. > > Which makes sense, yeah. > >> In case of the separate command, >> enabling responder will not update the beacon, >> however, the application must issue the new command, whenever its >> updating beacon template. > > 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) > In that case we definitely would need the > attribute to be 0/1 as you had it so that it not present can be used to > indicate "no change". OK. > > johannes
WARNING: multiple messages have this Message-ID (diff)
From: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> To: Johannes Berg <johannes@sipsolutions.net> Cc: linux-wireless-owner@vger.kernel.org, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Subject: Re: [PATCH 0/3] Add support for ftm responder configuration Date: Tue, 21 Aug 2018 15:08:02 -0700 [thread overview] Message-ID: <7999c366492a4523456227fb49329bf2@codeaurora.org> (raw) On 2018-08-21 12:24, Johannes Berg wrote: > On Tue, 2018-08-21 at 11:32 -0700, Pradeep Kumar Chitrapu wrote: >> >> I wasn't aware of this android api. > > OK. > >> However, looking at the api, the >> assumption is that bss is started by a different >> api and the 'enableResponder' api is used for enabling rtt for a given >> duration. > > It looks like. Note that there's also *disable*, which we hadn't even > implemented before. > >> The reason we have added enabling ftm responder through start ap is >> that >> this can reflect beacon IE change in the >> configuration in the same place. > > Which makes sense, yeah. > >> In case of the separate command, >> enabling responder will not update the beacon, >> however, the application must issue the new command, whenever its >> updating beacon template. > > 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) > In that case we definitely would need the > attribute to be 0/1 as you had it so that it not present can be used to > indicate "no change". OK. > > johannes _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2018-08-22 1:30 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-21 22:08 Pradeep Kumar Chitrapu [this message] 2018-08-21 22:08 ` [PATCH 0/3] Add support for ftm responder configuration Pradeep Kumar Chitrapu 2018-08-22 7:27 ` Johannes Berg 2018-08-22 7:27 ` Johannes Berg 2018-08-22 18:22 ` Pradeep Kumar Chitrapu 2018-08-22 18:22 ` Pradeep Kumar Chitrapu 2018-08-28 8:43 ` Johannes Berg 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 0:30 ` Pradeep Kumar Chitrapu 2018-08-15 9:04 ` Johannes Berg 2018-08-15 9:04 ` Johannes Berg 2018-08-16 1:50 ` pradeepc 2018-08-16 1:50 ` pradeepc 2018-08-16 8:12 ` Johannes Berg 2018-08-16 8:12 ` Johannes Berg 2018-08-18 7:50 ` Pradeep Kumar Chitrapu 2018-08-18 7:50 ` Pradeep Kumar Chitrapu 2018-08-20 9:33 ` Johannes Berg 2018-08-20 9:33 ` Johannes Berg 2018-08-21 18:32 ` Pradeep Kumar Chitrapu 2018-08-21 18:32 ` Pradeep Kumar Chitrapu 2018-08-21 19:24 ` Johannes Berg 2018-08-21 19:24 ` Johannes Berg 2018-08-16 9:21 ` Kalle Valo 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=7999c366492a4523456227fb49329bf2@codeaurora.org \ --to=pradeepc@codeaurora.org \ --cc=ath10k@lists.infradead.org \ --cc=johannes@sipsolutions.net \ --cc=linux-wireless-owner@vger.kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.