From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:65093 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751117Ab2JYWZv (ORCPT ); Thu, 25 Oct 2012 18:25:51 -0400 Received: by mail-wg0-f44.google.com with SMTP id dr13so1676654wgb.1 for ; Thu, 25 Oct 2012 15:25:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20121024194547.GA19060@shredder> <20121024220813.GB6723@shredder> From: Thomas Pedersen Date: Thu, 25 Oct 2012 15:25:28 -0700 Message-ID: (sfid-20121026_002554_731924_F1A690E4) Subject: Re: [ath9k-devel] ath9k_htc and reported mactime To: Adrian Chadd Cc: ath9k-devel@lists.ath9k.org, linux-wireless , Bob Copeland Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Oct 25, 2012 at 1:42 PM, Adrian Chadd wrote: > On 24 October 2012 18:54, Adrian Chadd wrote: > >> Yup, found it. The firmware TSF code was treating the TSF like it was >> an older pre-11n NIC and only dealing with the low handful of bits. >> Thomas has verified my test image works. >> >> I'll go and see about pushing this into the tree so Sujith's next >> ath9k_htc drop will include this fix. >> >> Thanks for the debugging info Thomas! > > Thomas, is the TSF in the RX status descriptor actually 32 bits, or is > this a printing error? Looking at the printk again, I'm pretty sure I'm just an idiot and the printed value is being truncated to 32 bits. Will test and verify the TSF wraps correctly again. Thomas From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Pedersen Date: Thu, 25 Oct 2012 15:25:28 -0700 Subject: [ath9k-devel] ath9k_htc and reported mactime In-Reply-To: References: <20121024194547.GA19060@shredder> <20121024220813.GB6723@shredder> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Thu, Oct 25, 2012 at 1:42 PM, Adrian Chadd wrote: > On 24 October 2012 18:54, Adrian Chadd wrote: > >> Yup, found it. The firmware TSF code was treating the TSF like it was >> an older pre-11n NIC and only dealing with the low handful of bits. >> Thomas has verified my test image works. >> >> I'll go and see about pushing this into the tree so Sujith's next >> ath9k_htc drop will include this fix. >> >> Thanks for the debugging info Thomas! > > Thomas, is the TSF in the RX status descriptor actually 32 bits, or is > this a printing error? Looking at the printk again, I'm pretty sure I'm just an idiot and the printed value is being truncated to 32 bits. Will test and verify the TSF wraps correctly again. Thomas