On Wed, 2011-03-16 at 23:03 +0200, ext Eliad Peller wrote: > When passing a tx frame, the driver incorrectly set desc->tid > with the ac instead of the actual tid. > > It has some serious implications when using 802.11n + QoS, > as the fw starts a BlockAck with the wrong tid (which finally > cause beacon loss and disconnection / some fw crash) > > Fix it by using the actual tid stored in skb->priority. How will the firmware handle the TIDs larger than 3, as currently to the firmware it appears only TID's 0-3 are configured, and the rest are whatever values happen to be there default? -Juuso -- 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
