From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Cahill, Ben M" <ben.m.cahill@intel.com>
Cc: iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: [ipw3945-devel] IWL3945 always reports noise levels of -127
Date: Tue, 05 May 2009 17:50:33 +0300 [thread overview]
Message-ID: <1241535034.4816.20.camel@maxim-laptop> (raw)
In-Reply-To: <02B3067C068D0549A8CCFCB17D4D318B3569A442@orsmsx502.amr.corp.intel.com>
On Mon, 2009-05-04 at 12:27 -0700, Cahill, Ben M wrote:
>
> >-----Original Message-----
> >From: Maxim Levitsky [mailto:maximlevitsky@gmail.com]
> >Sent: Monday, May 04, 2009 3:04 PM
> >To: Cahill, Ben M
> >Cc: iwlwifi maling list; linux-wireless
> >Subject: RE: [ipw3945-devel] IWL3945 always reports noise
> >levels of -127
> >
> >On Mon, 2009-05-04 at 11:53 -0700, Cahill, Ben M wrote:
> >> When one of our devices cannot figure out what the actual
> >noise level is, it reports -127.
> >>
> >> Newer devices are better at old devices at figuring noise
> >level. IIRC, 3945 cannot figure noise for CCK signals, and
> >may not be possible with OFDM as well.
> >
> >Why then it did work on older kernel ?
> >(and noise levels seemed to be correct)
>
> Hmmm, good point, and I don't know the answer! :-(
>
And I do know it now (this is what I suspected...)
This is firmware issue.
I forced the driver to use older firmware iwlwifi-3945-1.ucode,
and noise levels are back.
Regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-05 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 21:30 IWL3945 always reports noise levels of -127 Maxim Levitsky
2009-05-04 18:53 ` [ipw3945-devel] " Cahill, Ben M
2009-05-04 19:03 ` Maxim Levitsky
2009-05-04 19:27 ` Cahill, Ben M
2009-05-05 4:49 ` Maxim Levitsky
2009-05-05 14:50 ` Maxim Levitsky [this message]
2009-05-05 16:16 ` Maxim Levitsky
2009-05-05 18:45 ` Cahill, Ben M
2009-05-05 18:56 ` Maxim Levitsky
2009-05-08 23:25 ` reinette chatre
2009-05-10 12:02 ` Maxim Levitsky
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=1241535034.4816.20.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ben.m.cahill@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox