From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Chadd <adrian@freebsd.org>
Cc: freebsd-wireless@freebsd.org, linux-wireless@vger.kernel.org
Subject: Re: So, which IEEE<->Frequency mappings should we be all using?
Date: Mon, 22 Jul 2013 16:40:59 +0200 [thread overview]
Message-ID: <1374504059.14517.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAJ-Vmo=yvHUgv6pwK42n+NhPrAu9shxc5pigRkhZE+x91W_FoA@mail.gmail.com> (sfid-20130717_194238_629152_551DCEC6)
On Wed, 2013-07-17 at 10:42 -0700, Adrian Chadd wrote:
> * 420MHz
> * 700MHz
> * 900MHz (which we already have, due to history);
> * 3.6GHz
> * 4.9GHz
3.6 should have been defined in the spec recently, 4.9 surely is defined
already (though the whole stack will have to support the
dot11ChannelStartingFactor)
The others are kinda non-standard extensions, and you probably won't
even be able to properly support them since they're kinda
pretend-handled like 2.4 GHz.
johannes
next prev parent reply other threads:[~2013-07-22 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 17:42 So, which IEEE<->Frequency mappings should we be all using? Adrian Chadd
2013-07-18 0:58 ` Wright, Brett
2013-07-22 14:40 ` Johannes Berg [this message]
2013-07-22 17:35 ` Adrian Chadd
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=1374504059.14517.12.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=freebsd-wireless@freebsd.org \
--cc=linux-wireless@vger.kernel.org \
/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