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 _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
