History log of /freebsd-10.0-release/etc/regdomain.xml
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# 259065 07-Dec-2013 gjb

- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

# 256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


# 243974 07-Dec-2012 adrian

Add a new 900MHz GSM regulatory SKU for the Xagyl Communications XC900M.

The XC900M acts as a Ubiquiti XR9 (and I _think_ SR9) by default;
it uses the same 900MHz<->2.4GHz downconverter mapping.

However it has an alternative frequency mapping which squeezes in a couple
more half/quarter rate channels. Since the default HAL doesn't support
fractional tuning (sub-1MHz) in 2.4GHz mode on the AR5413/AR5414, they
implement it using a jumper.

Datasheet: http://www.xagyl.com/download/XC900M_Datasheet.pdf

Thankyou to Xagyl Communications for the XC900M NICs and Edgar Martinez
for organising the donation.

Tested:

* XC900M <-> XC900M
* Ubiquiti XR9 <-> XC900M

TODO:

* Test against SR9 and GZ901 if possible (the IEEE channel<->frequency
mapping may not match up, thanks to the slightly different channels
involved)


# 223998 14-Jul-2011 adrian

More Japan regulatory domain fixes:

* Add HT40 entries for the two new Japan bands
* Fix a channel separation bug in one of the new bands I introduced
in a previous commit.


# 223996 14-Jul-2011 adrian

Japan regulatory domain update #1 - sync with CRDA entries.

Specifics:

* add 4920MHz-4980MHz for 11a and 11n/HT20
* add 5040MHz-5080MHz for 11a and 11n/HT20
* add 5500MHz-5700MHz for 11a and 11n/HT20 (DFS needed)
* add 5500MHz-5680MHz for 11n/HT40 (DFS needed)

TODO:

* add correct HT40 bands for 4920-4980 and 5040-5080

For the curious:

There's been many revisions to the Japan regulatory rules.
Apparently, the requirements require old cards certified on a previous
version of the rules to obey the older rules, not the newer rules.

The regdomain.xml outlines the -current- restrictions.

The card driver (eg the ath_hal regulatory domain code) may include
previous revisions of the Japan rules.

The ath_hal regdomain code populates the initial channel list based on
what the EEPROM indicates is possible. The regdomain.xml database imposes
further restrictions on this.

So regdomain.xml only needs to have the -current- rules. If the card
was certified on an earlier set of JP rules, it may only support a subset
of those channels - these are calculated at device attach and this
restricted list is kicked to net80211. regdomain.xml operates on -this-
list of channels.

And thus, the correct regulatory behaviour for Japan is handled with only
one regdomain.xml Japan database entry.

(phew.)

Obtained from: Linux wireless-regdb


# 223564 26-Jun-2011 adrian

I think 23dBm is the correct value to use here. CRDA uses 20dBm + 3dB max antenna
gain; I believe net80211 doesn't take antenna gain into account and leaves it
up to the driver to enforce. (ath_hal(4) certainly tries to do this.)


# 223563 26-Jun-2011 adrian

Add a couple more frequency ranges to the FCC3 (FCC + DFS) regulatory domain.

The frequency range 5490MHz -> 5710MHz was opened up sometime in 2009, but
regdomain.xml wasn't updated.

FCC reference: (Section 15.407): http://louise.hallikainen.org/FCC/FccRules/2009/15/407/

The hole between 5600-5650MHz is due to a request from Airports using
a weather radar system which also utilises this range.
The GIT commit explaining this hole in more detail can be found here:

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=commit;h=fcbf9225d56e82d9a4e506187d42285e76d81523


# 223561 26-Jun-2011 adrian

Replace tab with 8 spaces, bringing it in line with the rest of the file.


# 223504 24-Jun-2011 adrian

Fix another broken HT40 channel band reference.


# 223498 24-Jun-2011 adrian

More incorrect HT/40 setups in FCC.

Noticed-by: bschmidt@


# 223497 24-Jun-2011 adrian

Fix an incorrect frequency band for HT/40 in the FCC SKU.

Noticed by: bschmidt@


# 223496 24-Jun-2011 adrian

Import one of the two missing US FCC DFS bands to FCC3.

The FCC opened up this band sometime in 2009 (and ath was updated);
but regdomain.xml wasn't updated.


# 208060 14-May-2010 dougb

Remove trailing white space. No functional changes.


# 187846 28-Jan-2009 sam

Remove gsm hacks now that we can do this "right":
o no need for special country codes; it's sufficient to use the sku
o no need to specify bands w/ 2.4G frequencies, use the real values
o remove duplicate band specs


# 187343 16-Jan-2009 sam

add FCC4 SKU to expose Public Safety Band (PSB) frequencies; this is
modeled after the Atheros SKU of the same name


# 186106 14-Dec-2008 sam

o fix DEBUG sku definition
o add definitions for 900MHz radios: Ubiquiti SR9 and XR9, and ZComax GZ-901


# 178355 20-Apr-2008 sam

802.11 regulatory definitions used by ifconfig

Support by: Hobnob