linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath9k: remove usage of deprecated noise value
Date: Tue, 27 Apr 2010 08:22:39 +0200	[thread overview]
Message-ID: <4BD682AF.6030206@free.fr> (raw)
In-Reply-To: <1272312561-22648-1-git-send-email-linville@tuxdriver.com>

John W. Linville a écrit :
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
>  drivers/net/wireless/ath/ath9k/common.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/common.c b/drivers/net/wireless/ath/ath9k/common.c
> index 09effde..b4424a6 100644
> --- a/drivers/net/wireless/ath/ath9k/common.c
> +++ b/drivers/net/wireless/ath/ath9k/common.c
> @@ -212,7 +212,6 @@ int ath9k_cmn_rx_skb_preprocess(struct ath_common *common,
>  	rx_status->mactime = ath9k_hw_extend_tsf(ah, rx_stats->rs_tstamp);
>  	rx_status->band = hw->conf.channel->band;
>  	rx_status->freq = hw->conf.channel->center_freq;
> -	rx_status->noise = common->ani.noise_floor;
>  	rx_status->signal = ATH_DEFAULT_NOISE_FLOOR + rx_stats->rs_rssi;
>  	rx_status->antenna = rx_stats->rs_antenna;
>  	rx_status->flag |= RX_FLAG_TSFT;
>   
Hey, I'm still using this value here in my setup (I've done some work on 
noise floor calibration and can submit a patch that report noise & 
signal values that makes more sense to me). I mentioned in an earlier 
patch that I was using the {last_signal, last_noise} debugfs file as 
well (in February, 17th).

Before removing noise reporting and all related code, wouln't it be 
better to have a replacement API? I was told that noise reporting is 
buggy for most chipset, but that's a bug in each driver, not in mac80211 
then. Such bugs could be fixed by using a default value of -101dBm 
(thermal noise at room temperature over a 20 MHz channel) if they are 
unable to determine a correct value.

Moreover, it is very convenient to have the {last_signal, last_noise} 
sampled at the same time and be in the same location. Likewise for the 
radiotap header, it is very easy to plot noise value over time if it is 
stored on a per packet basis. Of course, I know noise is a global 
property of the channel and not DEFINED on a per packet basis, but once 
you know that, it's still useful to have it REPORTED on a per packet basis.

So far, the solution for me was to revert the single patch for making 
the noise field deprecated, but I'm not going to revert each & every 
patches related to noise. After all, isn't it the purpose of peer review?

Regards,
Benoit


  reply	other threads:[~2010-04-27  6:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 20:09 [PATCH] ath9k: remove usage of deprecated noise value John W. Linville
2010-04-27  6:22 ` Benoit PAPILLAULT [this message]
2010-04-27 10:55   ` Joerg Pommnitz
2010-04-27 19:23     ` Benoit PAPILLAULT
2010-04-28 19:38       ` AW: " Joerg Pommnitz
2010-04-28 20:06         ` Benoit PAPILLAULT

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD682AF.6030206@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).