From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] avg-signal is weird in ath9k in 3.3.0
Date: Tue, 20 Mar 2012 12:47:52 -0700 [thread overview]
Message-ID: <4F68DEE8.60506@candelatech.com> (raw)
I'm testing out some code to get a stations's avg-signal through ethtool-stats,
and both it and /proc/net/wireless show ranges bouncing all over
(from around -48 to -110) on an interface running heavy traffic.
Are there any known bugs in 3.3.0 related to this?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: avg-signal is weird in ath9k in 3.3.0
Date: Tue, 20 Mar 2012 12:47:52 -0700 [thread overview]
Message-ID: <4F68DEE8.60506@candelatech.com> (raw)
I'm testing out some code to get a stations's avg-signal through ethtool-stats,
and both it and /proc/net/wireless show ranges bouncing all over
(from around -48 to -110) on an interface running heavy traffic.
Are there any known bugs in 3.3.0 related to this?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2012-03-20 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:47 Ben Greear [this message]
2012-03-20 19:47 ` avg-signal is weird in ath9k in 3.3.0 Ben Greear
2012-03-20 20:46 ` [ath9k-devel] " Ben Greear
2012-03-20 20:46 ` Ben Greear
2012-03-20 22:22 ` [ath9k-devel] " Felix Fietkau
2012-03-20 22:22 ` Felix Fietkau
2012-03-21 2:11 ` [ath9k-devel] " Ben Greear
2012-03-21 2:11 ` Ben Greear
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=4F68DEE8.60506@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.