On Wed, 12 Apr 2006 02:33:21 GMT, Larry Finger
<(E-Mail Removed)> wrote:
>I am working with the folks that are reverse engineering the Broadcom wireless driver for Linux.
Cool.
>Part of the job involves adding a software MAC layer to the ieee802.11 code. At present, each of the
>wireless drivers handles its own regulatory/geographical information. This leads to such absurdities
>as b/g drivers doing active scans for channels 1-14 everywhere in the world, even though channels
>12-14 are not allowed in the US, and AFAIK channel 14 is only allowed in Japan.
Americas (FCC)
2.412 to 2.462 GHz; 11 channels
5.15 to 5.35, 5.725 to 5.825 GHz; 12 channels
China
2.412 to 2.472 GHz; 13 channels
5.725 to 5.825 GHz; 4 channels
ETSI
2.412 to 2.472 GHz; 13 channels
5.15 to 5.35 GHz; 8 channels
5470 to 5725 MHz, 11 channels
Israel
2.432 to 2.472 GHz, 9 channels
5.15 to 5.35 GHz; 8 channels
Japan
2.412 to 2.472 GHz; 13 channels OFDM
2.412 to 2.484 GHz; 14 channels CCK
5.15 to 5.25 GHz; 4 channels
Japan2
2.412 to 2.472 GHz; 13 channels OFDM
2.412 to 2.484 GHz; 14 channels CCK
5.15 to 5.35 GHz; 8 channels
Korea
2.412 to 2.472 GHz; 13 channels
5.15 to 5.35, 5.46 to 5.72, 5.725 to 5.825, 19 channels
North America (not FCC)
2.412 to 2.462 GHz; 11 channels
5.15 to 5.35, 5.725 to 5.825 GHz; 12 channels
Singapore
2.412 to 2.472 GHz; 13 channels
5.15 to 5.35, 5.725 to 5.825 GHz; 12 channels
Taiwan
2.412 to 2.462 GHz; 11 channels
5.25 to 5.35, 5.725 to 5.825 GHz; 7 channels
>I have googled for every keyword I could think of, but have not found any sites that spell out the
>a/b/g channel and power restrictions in force throughout the world.
I couldn't find much either. This is the best I can offer:
|
http://www.cisco.com/en/US/products/...08059c96f.html
|
http://www.cisco.com/univercd/cc/td/...g/bkscgaxa.htm
|
http://www.cisco.com/univercd/cc/td/...u01/auappb.htm
|
http://www.intel.com/support/wireles...ide90/regs.htm
Trying to put that mess into a single coherent package is going to be
a major challenge.
>Most of what I have found is
>contained within the source code for the Intel ipw2200 driver, but that is given as obscure codes
>with little information regarding the regulatory jurisdiction. I also have the IEEE public
>documents, but they don't help much. Is there a site, or set of sites, the can provide this
>regulatory information?
>
>Thanks, Larry
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
(E-Mail Removed)
#
http://802.11junk.com (E-Mail Removed)
#
http://www.LearnByDestroying.com AE6KS