Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:50234 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758451Ab3BSQb3 (ORCPT ); Tue, 19 Feb 2013 11:31:29 -0500 Received: by mail-we0-f174.google.com with SMTP id r6so5805438wey.5 for ; Tue, 19 Feb 2013 08:31:28 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20130219134028.GA26332@pandem0nium> Date: Tue, 19 Feb 2013 08:31:25 -0800 Message-ID: (sfid-20130219_173133_844657_8DD165D7) Subject: Re: [ath9k-devel] improve operational ANI in Mesh mode From: Adrian Chadd To: Georgiewskiy Yuriy Cc: Simon Wunderlich , devel@lists.open80211s.org, ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Well, ANI does adjust some of its parameters based on the beacon signal level. It uses that as an estimate for how "strong" the signal is likely to be and tunes the baseband to either be highly sensitive or slightly on the deafer side. If you have many sources of beacons (read: ibss, mesh, TDMA in my case) then that particular feature of ANI can't be used and it should be disabled. The code should be special casing it. I suggest someone writes a bunch of test functions: * whether we see no beacons (ie, AP mode) * whether we see one set of beacons (ie, STA mode) * whether we see multiple sets of beacons (ie ,everything else) .. and then modify the ANI code to work with the above. adrian