From: "John W. Linville" <linville@tuxdriver.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: forrest@hifulltech.com, ath5k-devel@lists.ath5k.org,
mickflemm@gmail.com, jirislaby@gmail.com, lrodriguez@atheros.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: fix exp off-by-one when computing OFDM delta slope
Date: Wed, 13 May 2009 14:25:24 -0400 [thread overview]
Message-ID: <20090513182524.GF2680@tuxdriver.com> (raw)
In-Reply-To: <20090513151439.GA28476@hash.localnet>
On Wed, May 13, 2009 at 11:14:39AM -0400, Bob Copeland wrote:
>
> From: Forrest Zhang <forrest@hifulltech.com>
>
> Commit e8f055f0c3ba226ca599c14c2e5fe829f6f57cbb subtly changed the
> code that computes floating point values for the PHY3_TIMING register
> such that the exponent is off by a decimal point, which can cause
> problems with OFDM channel operation.
>
> get_bitmask_order() actually returns the highest bit set plus one,
> whereas the previous code wanted the highest bit set. Instead, use
> ilog2 which is what this code is really calculating. Also check
> coef_scaled to handle the (invalid) case where we need log2(0).
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> ---
>
> John, this plus 706d64453cce7179e05924c24d87777584a1275c fixes a
> regression for 2.6.30 5ghz operation (bugzilla 13077). Any chance
> they can both make it in? I can send a backport of this patch if
> you like (usual path change).
That's fine. But what about this last bit?
http://bugzilla.kernel.org/show_bug.cgi?id=13077#c6
Is that not needed?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-05-13 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 15:14 [PATCH] ath5k: fix exp off-by-one when computing OFDM delta slope Bob Copeland
2009-05-13 18:25 ` John W. Linville [this message]
2009-05-13 18:51 ` [ath5k-devel] " Bob Copeland
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=20090513182524.GF2680@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=forrest@hifulltech.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.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 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.