On 19 September 2014 20:28, <greearb@xxxxxxxxxxxxxxx> wrote: [...] > + /* If we are CT firmware, ask it to flush all tids on all peers on > + * all vdevs. Normal firmware will just crash if you do this. > + */ > + if (test_bit(ATH10K_FW_FEATURE_WMI_10X_CT, ar->fw_features)) > + ath10k_wmi_peer_flush(ar, 0xFFFFFFFF, peer_addr, 0xFFFFFFFF); I recall you've explained this some time ago, but can you refresh my memory, please? Is this any different from iterating over all peers and flushing each? Or does your firmware do so extra magic that is impossible to do with normal firmware commands? Michał -- 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
