Return-path: Received: from mail-wi0-f179.google.com ([209.85.212.179]:40221 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751704Ab3CZRQH (ORCPT ); Tue, 26 Mar 2013 13:16:07 -0400 Received: by mail-wi0-f179.google.com with SMTP id hn17so1213724wib.6 for ; Tue, 26 Mar 2013 10:16:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <5151D752.3080303@candelatech.com> References: <201303251712.19808.chunkeey@googlemail.com> <5151D752.3080303@candelatech.com> Date: Tue, 26 Mar 2013 10:16:05 -0700 Message-ID: (sfid-20130326_181612_617953_63D3A3BB) Subject: Re: [ath9k-devel] Auth Packet TX Delay From: Adrian Chadd To: Ben Greear Cc: Robert Shade , Christian Lamparter , ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org, Marco Fonseca Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: ... 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