From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 11 01:34:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C64196F9 for ; Fri, 11 Oct 2013 01:34:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 834242C5C for ; Fri, 11 Oct 2013 01:34:22 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id gc15so2758000qeb.15 for ; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=H22bSzuWssBN+yWynoquzw5bCO+zydZkxbaoSPAcJqk=; b=h5t0YrF2rA7isAchNPPD39NlbRq4APsDMxuB4bVgJqtU0II53rG1t1tnUqDqMTjWNM Xo+dQ393412Z8JyLnUMeVuOq7tt3OZp+R/jWujQk0gIxquoHz3CwuXPgmIAIoTXy67a2 2mQV3H3F9mrcSOD7EKpy3afgQbX5Srcgpj6kyvyqxbDop6/CqvkbRpYE90vDomOESJlf 2k8ySC9TikncPxFIEhLnyDYsSKuSrmXVV4XOrSxXhkOp/7zQ6BtJaMuxNpQDd+2PEF3z 2b8xDargH8v3l8i5wPh5BVfauBMyqMC5VQaYQAOx0GJRADeLIO16d9N5zRWNtTCTiGhC mkUw== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr4737677qeb.74.1381455261710; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 18:34:21 -0700 X-Google-Sender-Auth: EFpD7Chf2cru6sms4FFDR-osfBs Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: Adrian Chadd To: w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 01:34:22 -0000 I don't have any open source PHY documentation. :) I'd have to write it. Which isn't a bad thing; I'm happy to go and re-read what I (legally, legitimately!) have from Atheros about their PHY design and ANI and write up what's implemented in the driver. The thing with ANI is that a lot of the parameters (like self-correlation thresholds) have to do with how signal detection in the PHY works. So it's not specifically noise immunity as much as it's tweaking the sensitivity range and thresholds of the receiver hardware. There's some interesting things that should be re-investigated (ie, the m1/m2 thresholds and how weak signal detection works); I vaguely recall when I was working there that ANI was doing it "wrong". I'll setup a meeting or two with the PHY team when I'm back in California and jot down some further notes about this. -adrian (note: so I'm legally allowed to have all this stuff and I'm legally allowed to code up open source drivers with it, but what I can't do is share the documentation I have. So no, I won't share it. But whatever goes into open source to improve their chips is open/fair game. Hence, I can write documentation and discuss whatever ends up in the open source drivers..) On 10 October 2013 18:30, w wrote: > Do you have the open source link for the PHY documentation so I could rea= d > it? > > Actually my goal is quite simple I think: To test the effectiveness of AN= I. > > Thanks very much. > > ~ w ~ > > On Fri, Oct 11, 2013 at 4:43 AM, Adrian Chadd wrote: > > Yeah, it's all a bit confusing. I'd have to re-read the PHY > documentation i > > have here in order to really understand whta's going on. > > > > What are you trying to achieve herE? > > > > > > -adrian > > > > > > > > On 9 October 2013 20:03, w wrote: > >> > >> Update: looking at the patent again: > >> http://www.freepatentsonline.com/7349503.html > >> > >> Note that bb_m1thres and bb_m2thres refer to normalized, > >> self-correlated thresholds, bb_m2count_thr refers to the number of > >> self-correlation values (wherein a typical count would not exceed 31), > >> and bb_use_self_corr_low refers to an enabling bit value. > >> > >> (but the variables are still quite confusing.) > >> > >> > >> ~ w ~ > >> > >> On Thu, Oct 10, 2013 at 10:12 AM, w wrote: > >> > Yup, I read the patent. I have also read the Atheros documentation f= or > >> > ANI (for a different hardware version but it says the operation is > >> > similar). > >> > > >> > Are we able to see physical layer parameters like signal level / > >> > correlation / channel state information, > >> > or are they hidden inside the hardware? > >> > > >> > ~ w ~ > >> > > >> > > >> > > >> > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd > >> > wrote: > >> >> I'm not sure. I think it's a signal level. Have you read the ANI > >> >> patent(s) ? > >> >> > >> >> > >> >> > >> >> -adrian > >> >> > >> >> > >> >> > >> >> On 9 October 2013 19:04, w wrote: > >> >>> > >> >>> Is there any way I can printk the correlation values for > ar5416_ani.c? > >> >>> > >> >>> I couldn=92t find the variable that contains the correlation value= . > >> >>> Line 267 of the ar5416_ani.c file says: > >> >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, > >> >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); > >> >>> > >> >>> I don=92t know what the variables mean or what the function means = or > >> >>> what data type the variables are because I want to printk them. > >> >>> > >> >>> References: > >> >>> > >> >>> > >> >>> > >> >>> > http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani= .c?view=3Dmarkup > >> >>> > >> >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > >> >>> > >> >>> ~ w ~ > >> >>> _______________________________________________ > >> >>> freebsd-wireless@freebsd.org mailing list > >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >>> To unsubscribe, send any mail to > >> >>> "freebsd-wireless-unsubscribe@freebsd.org" > >> >> > >> >> > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to > >> "freebsd-wireless-unsubscribe@freebsd.org" > > > > >