> If raw results are mainly used for analysis algorithms how about > providing raw measurement data through debugfs. May even consider > adding rtt calculation in cfg80211/mac80211 for drivers that choose > to provide raw measurement data and still only report final RTT in > nl80211 api. > I think the "analysis algorithms" in this case are what actually gives you the distance value. However, I don't think we should accept that everybody wants to run their proprietary algorithms on top and expose only the values needed for those. That makes the drivers only usable with additional proprietary software, which may even be incompatible with the GPL. If the algorithms are in the device, then we can expose the final results, and that's most useful for applications in the API. If they're not, then we need to expose something that can be used without additional proprietary and device-specific algorithms. If those algorithms cannot be run in the device, then we should put them into the driver instead. johannes
