summaryrefslogtreecommitdiffstats
path: root/sys/kgssapi/gss_pname_to_uid.c
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2011-07-14 05:19:28 +0000
committeradrian <adrian@FreeBSD.org>2011-07-14 05:19:28 +0000
commitf495485b63d7102e4217dd4d013e711fa1802eca (patch)
tree9f34760fd32633fd8c27ccddb8984c4e8fa56a52 /sys/kgssapi/gss_pname_to_uid.c
parent0540cab05e06b998ae5adc49ba229170379539d2 (diff)
downloadFreeBSD-src-f495485b63d7102e4217dd4d013e711fa1802eca.zip
FreeBSD-src-f495485b63d7102e4217dd4d013e711fa1802eca.tar.gz
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
Diffstat (limited to 'sys/kgssapi/gss_pname_to_uid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud