As we've discussed with a number of people already, here's our current work to add fine timing measurement support. Most of the work is really done by the firmware, so this just defines the API. We've gone back and forth over this, and I guess one thing that might need explaining is the decision to only allow aborting a measurement by closing a socket. The reasoning behind this was that (a) it needs to be supported anyway, if the application crashes, and forcing it that way makes the code path more tested; (b) if you wanted to reuse a socket for this and other things, eventually you'd make your code more complex because you'd have to handle events while waiting for the ACK message for a command - but in most testing it'll work if you forget, and then randomly lose some events every once a while ... forcing a new socket also prevents that issue. Please send comments :) johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
