From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Radiotap Channel Bug
Date: Wed, 20 Aug 2014 07:04:18 +0200 [thread overview]
Message-ID: <CACna6rwBFAeCW2R+nq+7EALORdsFM+gT0-ne=vv6OUCGZOdAsw@mail.gmail.com> (raw)
In-Reply-To: <CAP-AUygR-351cngtV5f5NUyitdAay3+az4=_zkWij61wh7iByw@mail.gmail.com>
On 20 August 2014 01:36, Brandon Enochs <enochs.brandon@gmail.com> wrote:
> With CentOS 6.5, the LP phy type currently suffers from a calculation
> error in the way that it reports the channel on which a frame was
> received up through the mac80211 stack. It should use the
> b43_channel_to_freq_2ghz function; however, it uses the
> b43_freq_to_channel_2ghz instead. As a result, the radiotap header
> provides nonsensical values for the channel field. The following
> patch fixes this issue
Consider updating kernel to some newer version. I know 2.6.32 is a
still supported longterm, but it may miss some things anyway.
It seems the frequency fix was applied back to 3.2 longterm only.
next prev parent reply other threads:[~2014-08-20 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 23:36 Radiotap Channel Bug Brandon Enochs
2014-08-20 5:04 ` Rafał Miłecki [this message]
2014-08-20 13:02 ` Brandon Enochs
2014-08-20 13:09 ` Brandon Enochs
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='CACna6rwBFAeCW2R+nq+7EALORdsFM+gT0-ne=vv6OUCGZOdAsw@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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.