diff options
author | Luis R. Rodriguez <lrodriguez@atheros.com> | 2009-03-24 21:21:07 -0400 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2009-03-27 20:13:23 -0400 |
commit | 8a5117d80fe93de5df5b56480054f7df1fd20755 (patch) | |
tree | 12f7818ef99e7c170dc6484dc8f3f1bd52637a03 | |
parent | e4e72fb4de93e3d4047a4ee3f08778422e17ed0d (diff) |
cfg80211: default CONFIG_WIRELESS_OLD_REGULATORY to n
And update description and feature-removal schedule according
to the new plan.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
-rw-r--r-- | Documentation/feature-removal-schedule.txt | 13 | ||||
-rw-r--r-- | net/wireless/Kconfig | 37 |
2 files changed, 18 insertions, 32 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index 8365f52a3548..02ea3773535e 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
@@ -7,7 +7,7 @@ be removed from this file. | |||
7 | --------------------------- | 7 | --------------------------- |
8 | 8 | ||
9 | What: The ieee80211_regdom module parameter | 9 | What: The ieee80211_regdom module parameter |
10 | When: March 2010 | 10 | When: March 2010 / desktop catchup |
11 | 11 | ||
12 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, | 12 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, |
13 | and currently serves as an option for users to define an | 13 | and currently serves as an option for users to define an |
@@ -30,18 +30,23 @@ Who: Luis R. Rodriguez <lrodriguez@atheros.com> | |||
30 | 30 | ||
31 | --------------------------- | 31 | --------------------------- |
32 | 32 | ||
33 | What: old static regulatory information | 33 | What: CONFIG_WIRELESS_OLD_REGULATORY - old static regulatory information |
34 | When: 2.6.29 | 34 | When: March 2010 / desktop catchup |
35 | |||
35 | Why: The old regulatory infrastructure has been replaced with a new one | 36 | Why: The old regulatory infrastructure has been replaced with a new one |
36 | which does not require statically defined regulatory domains. We do | 37 | which does not require statically defined regulatory domains. We do |
37 | not want to keep static regulatory domains in the kernel due to the | 38 | not want to keep static regulatory domains in the kernel due to the |
38 | the dynamic nature of regulatory law and localization. We kept around | 39 | the dynamic nature of regulatory law and localization. We kept around |
39 | the old static definitions for the regulatory domains of: | 40 | the old static definitions for the regulatory domains of: |
41 | |||
40 | * US | 42 | * US |
41 | * JP | 43 | * JP |
42 | * EU | 44 | * EU |
45 | |||
43 | and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was | 46 | and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was |
44 | set. | 47 | set. We will remove this option once the standard Linux desktop catches |
48 | up with the new userspace APIs we have implemented. | ||
49 | |||
45 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> | 50 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
46 | 51 | ||
47 | --------------------------- | 52 | --------------------------- |
diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig index d1d18f34d272..3c3bc9e579ed 100644 --- a/net/wireless/Kconfig +++ b/net/wireless/Kconfig | |||
@@ -12,36 +12,17 @@ config CFG80211_REG_DEBUG | |||
12 | 12 | ||
13 | config WIRELESS_OLD_REGULATORY | 13 | config WIRELESS_OLD_REGULATORY |
14 | bool "Old wireless static regulatory definitions" | 14 | bool "Old wireless static regulatory definitions" |
15 | default y | 15 | default n |
16 | ---help--- | 16 | ---help--- |
17 | This option enables the old static regulatory information | 17 | This option enables the old static regulatory information |
18 | and uses it within the new framework. This is available | 18 | and uses it within the new framework. This option is available |
19 | temporarily as an option to help prevent immediate issues | 19 | for historical reasons and it is advised to leave it off. |
20 | due to the switch to the new regulatory framework which | 20 | |
21 | does require a new userspace application which has the | 21 | For details see: |
22 | database of regulatory information (CRDA) and another for | 22 | |
23 | setting regulatory domains (iw). | 23 | http://wireless.kernel.org/en/developers/Regulatory |
24 | 24 | ||
25 | For more information see: | 25 | Say N and if you say Y, please tell us why. The default is N. |
26 | |||
27 | http://wireless.kernel.org/en/developers/Regulatory/CRDA | ||
28 | http://wireless.kernel.org/en/users/Documentation/iw | ||
29 | |||
30 | It is important to note though that if you *do* have CRDA present | ||
31 | and if this option is enabled CRDA *will* be called to update the | ||
32 | regulatory domain (for US and JP only). Support for letting the user | ||
33 | set the regulatory domain through iw is also supported. This option | ||
34 | mainly exists to leave around for a kernel release some old static | ||
35 | regulatory domains that were defined and to keep around the old | ||
36 | ieee80211_regdom module parameter. This is being phased out and you | ||
37 | should stop using them ASAP. | ||
38 | |||
39 | Note: You will need CRDA if you want 802.11d support | ||
40 | |||
41 | Say Y unless you have installed a new userspace application. | ||
42 | Also say Y if have one currently depending on the ieee80211_regdom | ||
43 | module parameter and cannot port it to use the new userspace | ||
44 | interfaces. | ||
45 | 26 | ||
46 | config WIRELESS_EXT | 27 | config WIRELESS_EXT |
47 | bool "Wireless extensions" | 28 | bool "Wireless extensions" |