From: "John W. Linville" <linville@tuxdriver.com>
To: andy@warmcat.com
Cc: linux-wireless@vger.kernel.org,
Larry Finger <larry.finger@lwfinger.net>,
Michael Buesch <mb@bu3sch.de>,
johannes@sipsolutions.net
Subject: Re: [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel
Date: Thu, 19 Jul 2007 15:10:52 -0400 [thread overview]
Message-ID: <20070719191052.GC6603@tuxdriver.com> (raw)
In-Reply-To: <20070611103914.577674038@warmcat.com>
On Mon, Jun 11, 2007 at 11:38:30AM +0100, andy@warmcat.com wrote:
> bcm43xx-mac80211 is reporting bogus frequencies and channels back to
> mac80211 at the moment (eg, actual ch1 (2412MHz) reported as 2424MHz).
>
> Prior to this patch, the hardware rx channel value is reported as
> starting at 0x18 and rising by 0x0a per channel. Code in bcm43xx_xmit.c
> tries to take this value and add 2400 to it to get the rx frequency.
> It seems the intention is that the hardware reports the (rx freq - 2400),
> so we want the value starting at 0x0c and rising by 0x05 per channel.
>
> If the value read is shifted one more bit to the right, it will
> succeed in doing this. Therefore this patch increases the shifting constant
> by one and reduces the mask by one lsb.
>
> The rx frequency reported in the radiotap rx and then, eg, tcpdump,
> is then correct. I didn't test ch 14 but I guess the hardware is
> consistent about it.
>
> CC: Larry Finger <larry.finger@lwfinger.net>
> CC: Michael Buesch <mb@bu3sch.de>
> Signed-off-by: Andy Green <andy@warmcat.com>
Larry, Michael, Johannes -- ack/nak?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-19 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 10:38 [PATCH 0/2] Small driver fixes andy
2007-06-11 10:38 ` [PATCH 1/2] zd1211rw-mac80211: return hardware specific tx rate code for rx status andy
2007-07-19 19:10 ` John W. Linville
2007-07-19 21:19 ` Ulrich Kunitz
2007-06-11 10:38 ` [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel andy
2007-06-11 11:26 ` Johannes Berg
2007-06-11 11:45 ` Johannes Berg
2007-07-19 19:10 ` John W. Linville [this message]
2007-07-19 19:39 ` Michael Buesch
2007-07-20 6:05 ` Andy Green
2007-07-20 7:37 ` Johannes Berg
2007-07-20 13:31 ` John W. Linville
2007-07-20 14:36 ` Larry Finger
2007-07-20 14:47 ` Andy Green
2007-07-20 16:58 ` Larry Finger
2007-07-20 17:36 ` Michael Buesch
2007-07-20 17:48 ` Andy Green
2007-07-20 17:50 ` Michael Buesch
2007-07-20 20:40 ` 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=20070719191052.GC6603@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).