From: Johannes Berg <johannes@sipsolutions.net>
To: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, david.spinadel@intel.com
Subject: Re: [PATCH v3 0/3] support ftm responder configuration/statistics
Date: Thu, 06 Sep 2018 08:34:00 +0200 [thread overview]
Message-ID: <1536215640.4015.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1536195700-1351-1-git-send-email-pradeepc@codeaurora.org>
On Wed, 2018-09-05 at 18:01 -0700, Pradeep Kumar Chitrapu wrote:
> Currently ftm_responder parameter in hostapd.conf is only used for fine
> timing measurement (FTM) capability advertisement and actual control of
> the functionality is with low-level device/driver. This leads to confusion
> to the user when the capability advertisement is different from actual FTM
> responder functionality.
>
> For example, FTM responder capability advertisement is set to 'enabled',
> but the functionality is disabled or not supported by the driver.
>
> The patch set allows userspace to enable FTM responder functionality
> with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER
> with configurable lci/civic ocation parameters. Also extended feature flag
> is added for the drivers to advertise the support. Setting the flag to
> enable FTM responder would imply that AP responds to all FTM requests.
> Default is considered to be disabled.
>
> changes in V3:
> - fixed the ambiguous ftm responder disable case to be not supported
For reasons unknown to me, this patchset made it neither to the list
nor, consequently, patchwork. Please resend.
johannes
next prev parent reply other threads:[~2018-09-06 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 1:01 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu
2018-09-06 1:01 ` [PATCH v3 2/3] mac80211: support FTM " Pradeep Kumar Chitrapu
2018-09-06 1:01 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu
2018-09-06 6:34 ` Johannes Berg [this message]
2018-09-06 15:15 ` [PATCH v3 0/3] support ftm responder configuration/statistics Kalle Valo
2018-09-06 16:08 ` Johannes Berg
2018-09-06 16:18 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 17:06 Pradeep Kumar Chitrapu
2018-09-06 19:58 ` Johannes Berg
2018-09-07 9:23 ` Arend van Spriel
2018-09-06 21:11 Pradeep Kumar Chitrapu
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=1536215640.4015.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=david.spinadel@intel.com \
--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).