On Saturday 26 September 2009 10:14:38 Jouni Malinen wrote:
> This would depend on your use case.. I would have preferred
> absolute time since it allows the application to filter out
> entries that were not updated after the last scan request,
> i.e., to figure out which entries were found based on the last
> scan request (or well, based on frames received during this
> time).
Oh, we can still easily change that to an absolute time, if you
prefer. It's not yet upstream, AFAIK.
With the current patch, I'll still ignore scan results with an
age > 3 seconds. To make a decision about "which AP should I use
next", I don't need to know if the result was from this scan
request, or from the one before, or from a shell script doing
while true; do
iw xxx scan trigger freq 2412 essid SOME_AP
sleep 0.5
done
--
http://www.holgerschurig.de
--
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
