From: Dave <kilroyd@googlemail.com>
To: Richard Farina <sidhayn@gmail.com>
Cc: linux-wireless@vger.kernel.org, simon@thekelleys.org.uk,
jussi.kivilinna@mbnet.fi, acme@ghostprotocols.net,
pe1rxq@amsat.org
Subject: Re: [PATCH] wireless: Add channel/frequency conversions to ieee80211.h
Date: Tue, 23 Dec 2008 22:47:20 +0000 [thread overview]
Message-ID: <49516A78.9020402@gmail.com> (raw)
In-Reply-To: <495163C8.60003@gmail.com>
Richard Farina wrote:
> Dave wrote:
>> Richard Farina wrote:
>>> David Kilroy wrote:
>>>> Added mappings for FHSS, DSSS and OFDM channels - with macros to point
>>>> HR DSSS and ERP to the DSSS mappings. Currently just static inline
>>>> functions.
>>>> +static inline int ieee80211_ofdm_chan_to_freq(int s_freq, int channel)
>>>> +{
>>>> + if ((channel > 0) && (channel <= 200) &&
>>>> + (s_freq >= 4000))
>>>> + return s_freq + (channel * 5);
>>>> + else
>>>> + return -1;
>>>> +}
>>> Any desire to make 184-196 work? These are the 4.9 GHz channels.
>> Do you see a reason why these channels wouldn't work with these
>> conversion routines? Or are you asking about corresponding driver support?
> Channel 165 freq is 5825MHz
> Channel 183 freq is 4915MHz
>
> Since your method is linear and 183 is greater than 165, it will output
> a higher frequency for 183 than for 165 when converting from channel to
> freq.
I suspect you're talking about US regulatory class 5 which names channel
165 with a starting frequency of 5GHz, and Japans regulatory class 16-20
naming channel 183 with starting frequency 4GHz. These are accounted
for in the conversion routines by the s_freq parameter:
ieee80211_ofdm_chan_to_freq(5000, 165) ==> 5825
ieee80211_ofdm_chan_to_freq(4000, 183) ==> 4915
It means the caller must know the starting frequency when converting
OFDM channels and frequencies. I expect that this number will come from
the regulatory work that is underway (though I haven't been keeping
track of that).
Regards,
Dave.
>> If drivers don't currently support those channels, I suspect there's a
>> more significant issue to be addressed first.
> No drivers support these channels at the moment AFAIK but I'd be happy
> to submit a patch that enables tuning if someone else could submit a
> patch to support half/quarter clocked channels. Japan is the only place
> in the world that supports the 4.9GHz realm unlicensed, and I've already
> been told that patches that enabled licensed only features will not be
> accepted so I have not bothered to submit support as I lack the skill to
> add support for half/quarter clock channels and hence it wouldn't be
> unlicensed.
>
> Thanks,
> Rick Farina
next prev parent reply other threads:[~2008-12-23 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 14:03 [PATCH] wireless: Add channel/frequency conversions to ieee80211.h David Kilroy
2008-12-23 14:11 ` Arnaldo Carvalho de Melo
2008-12-23 16:09 ` Richard Farina
2008-12-23 20:22 ` Dave
2008-12-23 22:18 ` Richard Farina
2008-12-23 22:47 ` Dave [this message]
2008-12-23 20:30 ` Jeroen Vreeken
2008-12-24 21:57 ` Jussi Kivilinna
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=49516A78.9020402@gmail.com \
--to=kilroyd@googlemail.com \
--cc=acme@ghostprotocols.net \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=pe1rxq@amsat.org \
--cc=sidhayn@gmail.com \
--cc=simon@thekelleys.org.uk \
/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).