2009/7/29 Bob Copeland <me@xxxxxxxxxxxxxxx>: > We need to process tx descriptors for all queues (currently main tx > queue and cabq) which may have triggered the TX completion interrupt. > Otherwise, the queues can get stuck after sending a few frames. > > Also, the CAB queue does need to be DBA (DMA beacon alert) gated, as > in ath9k and madwifi, instead of beacon sent gated or the CAB frames > may not be sent at the right time. > I think we are doing the wrong thing, CAB queue is supposed to fire after beacon queue. Ath9k fires up cab queue and beacon queue at the same time and uses ready time to hold cab queue for a fixed interval. Try to remove the readytime stuff from cab queue and i guess it'll work fine (now we fire it after the beacon queue AND wait for a beacon transmition period). -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- 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
