diff options
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
| -rw-r--r-- | Documentation/feature-removal-schedule.txt | 37 |
1 files changed, 32 insertions, 5 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index e47c0ff8ba7a..02ea3773535e 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
| @@ -6,20 +6,47 @@ be removed from this file. | |||
| 6 | 6 | ||
| 7 | --------------------------- | 7 | --------------------------- |
| 8 | 8 | ||
| 9 | What: old static regulatory information and ieee80211_regdom module parameter | 9 | What: The ieee80211_regdom module parameter |
| 10 | When: 2.6.29 | 10 | When: March 2010 / desktop catchup |
| 11 | |||
| 12 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, | ||
| 13 | and currently serves as an option for users to define an | ||
| 14 | ISO / IEC 3166 alpha2 code for the country they are currently | ||
| 15 | present in. Although there are userspace API replacements for this | ||
| 16 | through nl80211 distributions haven't yet caught up with implementing | ||
| 17 | decent alternatives through standard GUIs. Although available as an | ||
| 18 | option through iw or wpa_supplicant its just a matter of time before | ||
| 19 | distributions pick up good GUI options for this. The ideal solution | ||
| 20 | would actually consist of intelligent designs which would do this for | ||
| 21 | the user automatically even when travelling through different countries. | ||
| 22 | Until then we leave this module parameter as a compromise. | ||
| 23 | |||
| 24 | When userspace improves with reasonable widely-available alternatives for | ||
| 25 | this we will no longer need this module parameter. This entry hopes that | ||
| 26 | by the super-futuristically looking date of "March 2010" we will have | ||
| 27 | such replacements widely available. | ||
| 28 | |||
| 29 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> | ||
| 30 | |||
| 31 | --------------------------- | ||
| 32 | |||
| 33 | What: CONFIG_WIRELESS_OLD_REGULATORY - old static regulatory information | ||
| 34 | When: March 2010 / desktop catchup | ||
| 35 | |||
| 11 | 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 |
| 12 | which does not require statically defined regulatory domains. We do | 37 | which does not require statically defined regulatory domains. We do |
| 13 | 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 |
| 14 | the dynamic nature of regulatory law and localization. We kept around | 39 | the dynamic nature of regulatory law and localization. We kept around |
| 15 | the old static definitions for the regulatory domains of: | 40 | the old static definitions for the regulatory domains of: |
| 41 | |||
| 16 | * US | 42 | * US |
| 17 | * JP | 43 | * JP |
| 18 | * EU | 44 | * EU |
| 45 | |||
| 19 | 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 |
| 20 | set. We also kept around the ieee80211_regdom module parameter in case | 47 | set. We will remove this option once the standard Linux desktop catches |
| 21 | some applications were relying on it. Changing regulatory domains | 48 | up with the new userspace APIs we have implemented. |
| 22 | can now be done instead by using nl80211, as is done with iw. | 49 | |
| 23 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> | 50 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 24 | 51 | ||
| 25 | --------------------------- | 52 | --------------------------- |