From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>,
Johannes Berg <johannes@sipsolutions.net>,
Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC PATCH] b43: Implement LP-PHY baseband table initialization
Date: Mon, 10 Aug 2009 11:02:49 -0500 [thread overview]
Message-ID: <4A8044A9.8090600@lwfinger.net> (raw)
In-Reply-To: <69e28c910908100842o6eecb131n50ff39fc48566880@mail.gmail.com>
Gábor Stefanik wrote:
> 2009/8/10 Larry Finger <Larry.Finger@lwfinger.net>:
>> Yes, that would work for the 2.4 GHz band, and I guess there could be
>> similar routines or macros to split the 5 GHz band into low, medium
>> and high channels.
>
> AFAIK there is no need to do that - using current_band for 2GHz is
> specifically to ensure that channels in the 2500...3000MHz range don't
> get parsed as 5GHz. There is currently no band above 5GHz used for
> wlan, so this problem can't show up on 5GHz.
OK.
> I'm gonna re-submit this as a formal patch soon.
Good.
I just noticed that
http://bcm-v4.sipsolutions.net/802.11/PHY/LP/Calibration is
incomplete. I'll work on that next.
Larry
next prev parent reply other threads:[~2009-08-10 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 1:00 [RFC PATCH] b43: Implement LP-PHY baseband table initialization Gábor Stefanik
2009-08-10 2:08 ` Larry Finger
2009-08-10 11:37 ` Gábor Stefanik
2009-08-10 14:55 ` Larry Finger
2009-08-10 15:42 ` Gábor Stefanik
2009-08-10 16:02 ` Larry Finger [this message]
2009-08-10 12:41 ` Michael Buesch
2009-08-10 12:49 ` Gábor Stefanik
2009-08-10 12:52 ` Michael Buesch
2009-08-10 17:19 ` Michael Buesch
2009-08-10 13:36 ` Holger Schurig
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=4A8044A9.8090600@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@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 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).