... and the odd thing here is that during scanning, it should be flushing the queues entirely so any new frame being transmitted _SHOULD_ result in: * TxDP for that queue being written (either FIFO or otherwise); * TxE for that queue being set. So unless the queue is "full" already and isn't being drained, I'm kinda curious as to why TX isn't starting. Adrian -- 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
