From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Pavel Roskin <proski@gnu.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Benoit PAPILLAULT <benoit.papillault@free.fr>,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH v3] mac80211: deprecate RX status noise
Date: Thu, 18 Feb 2010 15:41:45 +0100 [thread overview]
Message-ID: <201002181541.45835.holgerschurig@gmail.com> (raw)
In-Reply-To: <1266494831.6261.1.camel@jlt3.sipsolutions.net>
> Various hardware reports various bogus values, like iwlwifi for
> example reporting the same noise value that it collected after
> a beacon over and over again, or just reporting 127 when it had
> no value.
I'm not saying that I understand this completely, but for me it
would make sense to disable iwlwifi's broken noise reporting
only. No reason to disable it for everyone if some of them are
broken.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2010-02-18 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:05 [PATCH] mac80211: deprecate RX status noise Johannes Berg
2010-02-17 20:22 ` [PATCH v2] " Johannes Berg
2010-02-17 20:27 ` [PATCH v3] " Johannes Berg
2010-02-17 20:48 ` Benoit PAPILLAULT
2010-02-17 22:29 ` Luis R. Rodriguez
2010-02-17 22:51 ` Pavel Roskin
2010-02-18 12:07 ` Johannes Berg
2010-02-18 14:41 ` Holger Schurig [this message]
2010-02-18 14:48 ` Johannes Berg
2010-02-18 19:57 ` Kalle Valo
2010-02-18 20:27 ` Luis R. Rodriguez
[not found] ` <7f9d9abf1002181728q63c9f090je175681bc520f0ad@mail.gmail.com>
2010-02-20 11:06 ` Johannes Berg
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=201002181541.45835.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=benoit.papillault@free.fr \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.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.