From: Kalle Valo <kvalo@adurom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl1251: add get_survey callback in order to get channel noise
Date: Wed, 28 Jul 2010 23:36:11 +0300 [thread overview]
Message-ID: <4C5094BB.6070105@adurom.com> (raw)
In-Reply-To: <1280345147-24137-1-git-send-email-linville@tuxdriver.com>
On 07/28/2010 10:25 PM, John W. Linville wrote:
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> The calculation of the noise value looks a bit strange to me, but this
> is the same calculation from commit 446cfaa412beef0dd6cb0edf3b4eaed34d824537,
> some hopefully it was/is correct (or good enough)...
I never was able to find out proper way to measure noise with wl1251.
The algorithm I came up and included in this patch is most likely
incorrect. But as having support for noise survey doesn't do any harm,
and hopefully we even might motivate someone to fix the algorithm, I
think it's safe to have this patch.
Acked-by: Kalle Valo <kvalo@adurom.com>
prev parent reply other threads:[~2010-07-28 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 19:25 [PATCH] wl1251: add get_survey callback in order to get channel noise John W. Linville
2010-07-28 20:36 ` Kalle Valo [this message]
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=4C5094BB.6070105@adurom.com \
--to=kvalo@adurom.com \
--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).