On Mon, 2010-02-15 at 23:36 +0100, Benoit PAPILLAULT wrote: > Just for my own understanding. It seems the implementation has 2 > different code path : > - "real" monitor mode which is handled right after ieee80211_rx() so > it > is not affected > - "cook" monitor mode which is handled as part of the RX handlers. > > BTW, why do we have 2 different code path? I'm sure I missed something > > obvious here. cooked monitor reports only usable, decrypted frames that the kernel didn't know how to handle. 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
