From: Johannes Berg <johannes@sipsolutions.net>
To: Bruno Randolf <br1@einfach.org>
Cc: Dave Kilroy <kilroyd@googlemail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC] mac80211: Extend channel to frequency mapping for 802.11j
Date: Tue, 28 Dec 2010 10:51:01 +0100 [thread overview]
Message-ID: <1293529861.3526.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201012281843.57453.br1@einfach.org>
On Tue, 2010-12-28 at 18:43 +0900, Bruno Randolf wrote:
> > You don't have to use them, but there are a few channel/frequency
> > conversion routines in include/ieee80211.h which could be reused in
> > these functions.
>
> Thanks for that info, I didn't know about those functions. I just checked
> them and it seems most of them are not used, AFAICT:
>
> ieee80211_fhss_chan_to_freq - not used
> ieee80211_freq_to_fhss_chan - not used
> ieee80211_hr_chan_to_freq - not used
> ieee80211_freq_to_hr_chan - not used
> ieee80211_erp_chan_to_freq - not used
> ieee80211_freq_to_erp_chan - not used
> ieee80211_ofdm_chan_to_freq - not used
> ieee80211_freq_to_ofdm_chan - not used
Cute -- we should probably just remove these.
> The only two which are used are for 2GHz channels:
>
> ieee80211_dsss_chan_to_freq - atmel, airo, wl3501_cs, orinoco, rndis_wlan
> ieee80211_freq_to_dsss_chan - atmel, airo, orinoco, zd1201
>
> Anyhow i guess it would make sense to have a common channel to frequency
> mapping function for mac80211 and other wireless drivers? The problem is now
> we have to use enum ieee80211_band which is defined cfg80211.h...
Well, you're a bit wrong -- the function you're modifying is part of
cfg80211. Therefore, including cfg80211.h makes perfect sense, it's also
defined in there (therefore, your patch subject should begin with
"cfg80211:" instead of "mac80211:").
However, of those drivers you list only orinoco and rndis_wlan already
use cfg80211, so for the others using it would introduce an almost
"fake" dependency. In any case, it seems like all that should be
separate patches.
johannes
next prev parent reply other threads:[~2010-12-28 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 7:44 [PATCH RFC] mac80211: Extend channel to frequency mapping for 802.11j Bruno Randolf
2010-12-24 16:46 ` Dave Kilroy
2010-12-28 9:43 ` Bruno Randolf
2010-12-28 9:51 ` Johannes Berg [this message]
2010-12-28 9:53 ` Johannes Berg
2010-12-29 13:55 ` Dave Kilroy
2010-12-27 10:57 ` Johannes Berg
2010-12-28 5:31 ` Bruno Randolf
2010-12-28 8:38 ` Johannes Berg
2010-12-28 9:01 ` Jouni Malinen
2010-12-28 9:08 ` Johannes Berg
2010-12-28 9:25 ` Jouni Malinen
2010-12-28 9:39 ` Bruno Randolf
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=1293529861.3526.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=br1@einfach.org \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).