Bernhard Schmidt 3934c8a53f Fix scanning after loosing a connection. The firmware assumes that as long ... as an association ID is set any scan is supposed to be a background scan. This implies that the firmware will switch back to the associated channel after a certain threshold, though, we are not notified about that. We currently catch this case by a timer which will reset the firmware after a 'scan timeout', though, upper layers are not notified about that and will simply hang until manual intervention. Fix this by resetting the firmware's knowledge about any association on RUN -> ASSOC and !INIT -> SCAN transitions. Tested by: Zhihao Yuan <lichray at gmail.com> MFC after: 1 week		2010-12-06 19:05:44 +00:00
..
if_wpi.c	Fix scanning after loosing a connection. The firmware assumes that as long	2010-12-06 19:05:44 +00:00
if_wpireg.h	o) Check that no overrun or CRC errors were encountered in receiving a	2009-03-27 03:17:25 +00:00
if_wpivar.h	net80211 rate control framework (net80211 ratectl).	2010-04-07 15:29:13 +00:00