On Wed, 2018-08-22 at 11:22 -0700, Pradeep Kumar Chitrapu wrote: > > Should we just ignore that? Or perhaps add a separate capability for > > it? > > Yes, even we behave the same. In that case, we can go ahead now with the > capability to only enable FTM responder. If the driver wants to support > disabling option in future, at which point, the new capability can be > added. True. > However, changes to nl80211_set_beacon to support enabling FTM responder > may still be needed along with start_ap, assuming that ap start will be > issued by different android api than enableResponder api. Yes, I guess that's still needed to be able to support the Android API, which seems useful. johannes
