From: Johannes Berg <johannes@sipsolutions.net>
To: Bruno Randolf <br1@einfach.org>
Cc: Brian Prodoehl <bprodoehl@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Dan Williams <dcbw@redhat.com>,
libertas-dev@lists.infradead.org,
Ivo van Doorn <IvDoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
users@rt2x00.serialmonkey.com
Subject: Re: [PATCH] cfg80211: Extend channel to frequency mapping for 802.11j
Date: Tue, 11 Jan 2011 13:18:49 +0100 [thread overview]
Message-ID: <1294748329.3611.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201101111817.40309.br1@einfach.org>
On Tue, 2011-01-11 at 18:17 +0900, Bruno Randolf wrote:
> > compat-wireless-2011-01-07.orig/drivers/net/wireless/libertas/cfg.c 2011-0
> > 1-07 15:03:59.000000000 -0500
> > +++
> > compat-wireless-2011-01-07/drivers/net/wireless/libertas/cfg.c 2011-01-08
> > 07:51:23.947290769 -0500
> > @@ -607,7 +607,8 @@
> > /* No channel, no luck */
> > if (chan_no != -1) {
> > struct wiphy *wiphy = priv->wdev->wiphy;
> > - int freq = ieee80211_channel_to_frequency(chan_no);
> > + int freq = ieee80211_channel_to_frequency(chan_no,
> > + chan_no <= 14 ? IEEE80211_BAND_2GHZ :
> IEEE80211_BAND_5GHZ);
>
> The whole point of having the band argument is to avoid this. We now have
> overlapping channel numbers: channel 8 and 12 are defined in 5GHz as well as
> in 2.4GHz (that is for 20MHz channel width, there are more for 10 and 5MHz
> width, but we don't support that yet). The band has to come from the hardware
> or driver configuration.
I don't think libertas (or orinoco) support the frequencies that
overlap, and they use the channel number in HW config, so it should be
fine.
johannes
next prev parent reply other threads:[~2011-01-11 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 5:26 [PATCH] cfg80211: Extend channel to frequency mapping for 802.11j Bruno Randolf
2011-01-07 11:43 ` Johannes Berg
2011-01-07 12:45 ` Brian Prodoehl
2011-01-07 12:53 ` Brian Prodoehl
2011-01-08 3:43 ` Bruno Randolf
2011-01-08 13:08 ` Brian Prodoehl
2011-01-11 9:17 ` Bruno Randolf
2011-01-11 12:18 ` Johannes Berg [this message]
2011-01-11 13:16 ` Brian Prodoehl
2011-01-11 15:09 ` Dan Williams
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=1294748329.3611.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=IvDoorn@gmail.com \
--cc=bprodoehl@gmail.com \
--cc=br1@einfach.org \
--cc=dcbw@redhat.com \
--cc=gwingerde@gmail.com \
--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 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.