On 01/20/2011 09:37 AM, Johannes Berg wrote:
On Thu, 2011-01-20 at 09:32 -0800, greearb@xxxxxxxxxxxxxxx wrote:
From: Ben Greear<greearb@xxxxxxxxxxxxxxx>
This method is called when driver can support
scanning the currect active channel without otherwise
impeding traffic on that channel. The mac80211 scan
logic may call this when we are only scanning on the
active channel and thus do not need to go off channel.
I frankly don't see any point telling the driver about this. Looking at
the ath9k patch you sent, it seems to avoid some things like flushing --
but the flushing should be controlled by mac80211 already (or converted
to be) so that it's not necessary to have this.
mac80211 + ath9k is a house of cards, and this seemed the least
invasive approach. It also lets us not change behaviour for
the rest of the drivers until they are audited and potentially
updated. At best I can test/hack on ath5k and ath9k. These are
touchy enough, and other drivers may be even more twitchy...
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
