@@ -6,20 +6,47 @@ be removed from this file.
66
77---------------------------
88
9- What: old static regulatory information and ieee80211_regdom module parameter
10- When: 2.6.29
9+ What: The ieee80211_regdom module parameter
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+
1136Why: The old regulatory infrastructure has been replaced with a new one
1237 which does not require statically defined regulatory domains. We do
1338 not want to keep static regulatory domains in the kernel due to the
1439 the dynamic nature of regulatory law and localization. We kept around
1540 the old static definitions for the regulatory domains of:
41+
1642 * US
1743 * JP
1844 * EU
45+
1946 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
21- some applications were relying on it. Changing regulatory domains
22- can now be done instead by using nl80211, as is done with iw.
47+ set. We will remove this option once the standard Linux desktop catches
48+ up with the new userspace APIs we have implemented.
49+
2350Who: Luis R. Rodriguez <lrodriguez@atheros.com>
2451
2552---------------------------
@@ -229,7 +256,9 @@ Who: Jan Engelhardt <jengelh@computergmbh.de>
229256---------------------------
230257
231258What: b43 support for firmware revision < 410
232- When: July 2008
259+ When: The schedule was July 2008, but it was decided that we are going to keep the
260+ code as long as there are no major maintanance headaches.
261+ So it _could_ be removed _any_ time now, if it conflicts with something new.
233262Why: The support code for the old firmware hurts code readability/maintainability
234263 and slightly hurts runtime performance. Bugfixes for the old firmware
235264 are not provided by Broadcom anymore.
@@ -344,3 +373,20 @@ Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
344373 Removal is subject to fixing any remaining bugs in ACPI which may
345374 cause the thermal throttling not to happen at the right time.
346375Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
376+
377+ -----------------------------
378+
379+ What: __do_IRQ all in one fits nothing interrupt handler
380+ When: 2.6.32
381+ Why: __do_IRQ was kept for easy migration to the type flow handlers.
382+ More than two years of migration time is enough.
383+ Who: Thomas Gleixner <tglx@linutronix.de>
384+
385+ -----------------------------
386+
387+ What: obsolete generic irq defines and typedefs
388+ When: 2.6.30
389+ Why: The defines and typedefs (hw_interrupt_type, no_irq_type, irq_desc_t)
390+ have been kept around for migration reasons. After more than two years
391+ it's time to remove them finally
392+ Who: Thomas Gleixner <tglx@linutronix.de>
0 commit comments