All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] RE :  [AR9280] unable to get noise level
Date: Fri, 15 Oct 2010 09:26:00 -0700	[thread overview]
Message-ID: <4CB88098.9070304@candelatech.com> (raw)
In-Reply-To: <12429_1287146103_4CB84A77_12429_44117_1_47271B538B94C245B47E389DBCBE1D8F3F24E766F6@PUEXCB2C.nanterre.francetelecom.fr>

On 10/15/2010 05:35 AM, mickael.masson at orange-ftgroup.com wrote:
> Hi Mohammed, Hi all,
>
> We tried with the latest compat-wireless tree (as explained in http://wireless.kernel.org/en/users/Download/hacking#Git_trees_you_will_need) and we got same results with the command:
> $ cat /proc/net/wireless
> Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
>   face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
>   wlan1: 0000   30.  -80.  -256        0      0      0     14     18        0
>   wlan2: 0000    0     0     0        0      0      0      0      0        0
> mon.wlan2: 0000    0     0     0        0      0      0      0      0        0
>
> Noise is always equal to -256.
> We knew that API changed when<iw>  tool was released (and consequently<wireless-tool>  was deprecated) but we thougth that read /proc/net/wireless would still provide reliable information. It seems that we were wrong!

I'm attaching patches to make this work, but the maintainers are not interested in these
patches upstream last I checked, so you'll have to apply them yourself.

The status/flags part of the patch is a real hack (exposes internal flags field with
no translation), but it can show you if the interfaces are scanning or not, etc.

This patch also shows current rate as a new field in /proc/net/wireless.

Please let me know if you have any questions.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-wext-Add-noise-flags-and-rate-to-proc-net-wireless.patch
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20101015/cb330057/attachment-0001.txt 

  parent reply	other threads:[~2010-10-15 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 13:45 [ath9k-devel] [AR9280] unable to get noise level mickael.masson at orange-ftgroup.com
     [not found] ` <AANLkTikoGr8+jvrVWucvDS+FxaxKRdKs2x0y7aQ7k9gL@mail.gmail.com>
2010-10-15 12:35   ` [ath9k-devel] RE : " mickael.masson at orange-ftgroup.com
2010-10-15 14:34     ` Mohammed Shafi
2010-10-15 16:26     ` Ben Greear [this message]
2010-10-15 17:58       ` Luis R. Rodriguez
2010-10-19  8:35       ` [ath9k-devel] RE : " mickael.masson at orange-ftgroup.com

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=4CB88098.9070304@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.