From: "Bjørn Mork" <bjorn@mork.no>
To: margitsw@t-online.de (Margit Schubert-While)
Cc: netdev@oss.sgi.com, jgarzik@pobox.com, prism54-devel@prism54.org
Subject: Re: [PATCH Linux-2.6.7-bk19] prism54 freq to channel incorrect for 5GHz
Date: Wed, 07 Jul 2004 09:49:11 +0200 [thread overview]
Message-ID: <hvhdskl0js.fsf@rasputin.ws.nextra.no> (raw)
In-Reply-To: <200407070831.47896.margitsw@t-online.de> (Margit Schubert-While's message of "Wed, 7 Jul 2004 08:31:47 +0200")
margitsw@t-online.de (Margit Schubert-While) writes:
> Note that AFAIK, the 5GHz WLAN channels start at 34 (5.17 GHz)
> (but I am not sure)
802.11a defines all channels 0..200, i.e. all center frequencies from
5 to 6 GHz. But I don't know any country which allows usage of the 5 GHz
band below 5150 MHz, and the lowest channel should be at least 20 MHz
from the band edge, so 34 is probably the lowest channel that legally
can be used anywhere (and I believe 36 is the lowest allowed in the US?)
> and I don't know the top limit (except that
> it is <= 6GHz). Maybe somebody can shed light on this.
The highest available frequency (in Europe at least) is 5875 MHz.
Which would make 171 the highest available channel (given a 20 MHz
minimum distance from the center frequency to the band edge).
> Apparently Japan is doing something in the 10GHz band -
> will have to look for details.
That would require a new PHY standard.
Bjørn
next prev parent reply other threads:[~2004-07-07 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 6:31 [PATCH Linux-2.6.7-bk19] prism54 freq to channel incorrect for 5GHz Margit Schubert-While
2004-07-07 7:49 ` Bjørn Mork [this message]
2004-07-08 18:43 ` Vladimir Kondratiev
2004-07-09 6:58 ` Vladimir Kondratiev
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 15:38 Margit Schubert-While
2004-07-06 15:50 ` Sam Leffler
2004-07-07 5:02 ` Jeff Garzik
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=hvhdskl0js.fsf@rasputin.ws.nextra.no \
--to=bjorn@mork.no \
--cc=jgarzik@pobox.com \
--cc=margitsw@t-online.de \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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;
as well as URLs for NNTP newsgroup(s).