On Mon, 2013-02-11 at 13:24 +0530, Krishna Chaitanya wrote: > On Thu, Feb 7, 2013 at 8:57 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > On Thu, 2013-02-07 at 16:18 +0100, Felix Fietkau wrote: > > > >> > But whats the use of sending an AMSDU if we are not connected? > >> > First check in the code is to check for a connection. > >> I mentioned cooked monitor because putting the hw in monitor mode may > >> not always be desirable, and cooked monitor bypasses that. > > > > You can pass "flags none" on the iw command line and it shouldn't change > > much then, but yeah, still might do a few other things. Anyway cooked > > should work fine. > > Even in the cooked monitor case, the setting of qos_header is done > in the ieee80211_xmit(), so we still need to have some flag to know > if its an AMSDU/Not based, even if we set the bit in the user space > this will overwrite that. You should be able to patch this very easily to preserve the A-MSDU bit, which won't matter in the normal case where it's always cleared. 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
