linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: Bruno Randolf <br1@einfach.org>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"gwingerde@gmail.com" <gwingerde@gmail.com>,
	"libertas-dev@lists.infradead.org"
	<libertas-dev@lists.infradead.org>,
	"dcbw@redhat.com" <dcbw@redhat.com>,
	"IvDoorn@gmail.com" <IvDoorn@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
	"bprodoehl@gmail.com" <bprodoehl@gmail.com>
Subject: Re: [PATCH 2] cfg80211: Extend channel to frequency mapping for 802.11j
Date: Fri, 21 Jan 2011 14:16:13 +0200	[thread overview]
Message-ID: <1295612173.1925.59.camel@pimenta> (raw)
In-Reply-To: <20110117043728.8024.13541.stgit@localhost6.localdomain6>

On Mon, 2011-01-17 at 05:37 +0100, Bruno Randolf wrote:
> Extend channel to frequency mapping for 802.11j Japan 4.9GHz band, according to
> IEEE802.11 section 17.3.8.3.2 and Annex J. Because there are now overlapping
> channel numbers in the 2GHz and 5GHz band we can't map from channel to
> frequency without knowing the band. This is no problem as in most contexts we
> know the band. In places where we don't know the band (and WEXT compatibility)
> we assume the 2GHz band for channels below 14.
> 
> This patch does not implement all channel to frequency mappings defined in
> 802.11, it's just an extension for 802.11j 20MHz channels. 5MHz and 10MHz
> channels as well as 802.11y channels have been omitted.
> 
> The following drivers have been updated to reflect the API changes:
> iwl-3945, iwl-agn, iwmc3200wifi, libertas, mwl8k, rt2x00, wl1251, wl12xx.
> The drivers have been compile-tested only.
> 
> Signed-off-by: Bruno Randolf <br1@einfach.org>
> 
> ---

For the wl12xx part:

> diff --git a/drivers/net/wireless/wl12xx/rx.c b/drivers/net/wireless/wl12xx/rx.c
> index 682304c..ec8d843 100644
> --- a/drivers/net/wireless/wl12xx/rx.c
> +++ b/drivers/net/wireless/wl12xx/rx.c
> @@ -76,7 +76,7 @@ static void wl1271_rx_status(struct wl1271 *wl,
>          */
>         wl->noise = desc->rssi - (desc->snr >> 1);
> 
> -       status->freq = ieee80211_channel_to_frequency(desc->channel);
> +       status->freq = ieee80211_channel_to_frequency(desc->channel, desc_band);
> 
>         if (desc->flags & WL1271_RX_DESC_ENCRYPT_MASK) {
>                 status->flag |= RX_FLAG_IV_STRIPPED | RX_FLAG_MMIC_STRIPPED;

Acked-by: Luciano Coelho <coelho@ti.com>

-- 
Cheers,
Luca.


      parent reply	other threads:[~2011-01-21 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17  4:37 [PATCH 2] cfg80211: Extend channel to frequency mapping for 802.11j Bruno Randolf
2011-01-17 20:17 ` Brian Prodoehl
2011-01-18  1:06   ` Bruno Randolf
2011-01-18  2:42     ` Brian Prodoehl
2011-01-18  2:50       ` Bruno Randolf
2011-01-21 12:16 ` Luciano Coelho [this message]

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=1295612173.1925.59.camel@pimenta \
    --to=coelho@ti.com \
    --cc=IvDoorn@gmail.com \
    --cc=bprodoehl@gmail.com \
    --cc=br1@einfach.org \
    --cc=dcbw@redhat.com \
    --cc=gwingerde@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=users@rt2x00.serialmonkey.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).