On Sun, Nov 01, 2009 at 03:41:49PM +0200, Nick Kossifidis wrote: > So beacon-sent gated option doesn't work ? > Did you try also AR5K_DCU_MISC_ARBLOCK_IGNORE ? No, but I'll try that today. > Also according to docs Beacon frames should use queue 9 and CAB should > use queue 8 (don't know why but docs say that these are the > appropriate DCUs), beacon-gated triggering might only work if we use > DCU 9 for beacons (now we are using queue 7 for beacons and queue 6 > for cab). Yeah, I read the same thing. The docs say 8 and 9 are highest priority queues, it also says they both need to be DBA gated, but then on the other hand it describes beacon-sent gated as precisely what we want, and that queue 8 is "typically associated with beacon-gated frames." I originally assumed the queue with AR5K_DCU_MISC_BCN_ENABLE is used for triggering beacon sent but I'll try renumbering the queues and see what happens. Just copying ath9k list in case anyone with the inside scoop from Atheros wants to chime in. :) The issue is queue settings for the CAB queue. Beacon sent gating seems like a better option than using time throttled DBA gating (with ready time for the next beacon interval). Ath9k is using the latter, the former seems not to work at least in ath5k, or we're doing it wrong. -- Bob Copeland %% www.bobcopeland.com -- 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
