Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | The following is a list of files and features that are going to be |
| 2 | removed in the kernel source tree. Every entry should contain what |
| 3 | exactly is going away, why it is happening, and who is going to be doing |
| 4 | the work. When the feature is removed from the kernel, it should also |
| 5 | be removed from this file. |
| 6 | |
| 7 | --------------------------- |
| 8 | |
Luis R. Rodriguez | 4d8cd26 | 2009-09-08 12:09:47 -0700 | [diff] [blame] | 9 | What: PRISM54 |
| 10 | When: 2.6.34 |
| 11 | |
| 12 | Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the |
| 13 | prism54 wireless driver. After Intersil stopped selling these |
| 14 | devices in preference for the newer more flexible SoftMAC devices |
| 15 | a SoftMAC device driver was required and prism54 did not support |
| 16 | them. The p54pci driver now exists and has been present in the kernel for |
| 17 | a while. This driver supports both SoftMAC devices and FullMAC devices. |
| 18 | The main difference between these devices was the amount of memory which |
| 19 | could be used for the firmware. The SoftMAC devices support a smaller |
| 20 | amount of memory. Because of this the SoftMAC firmware fits into FullMAC |
| 21 | devices's memory. p54pci supports not only PCI / Cardbus but also USB |
| 22 | and SPI. Since p54pci supports all devices prism54 supports |
| 23 | you will have a conflict. I'm not quite sure how distributions are |
| 24 | handling this conflict right now. prism54 was kept around due to |
| 25 | claims users may experience issues when using the SoftMAC driver. |
| 26 | Time has passed users have not reported issues. If you use prism54 |
| 27 | and for whatever reason you cannot use p54pci please let us know! |
| 28 | E-mail us at: linux-wireless@vger.kernel.org |
| 29 | |
| 30 | For more information see the p54 wiki page: |
| 31 | |
| 32 | http://wireless.kernel.org/en/users/Drivers/p54 |
| 33 | |
| 34 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 35 | |
| 36 | --------------------------- |
| 37 | |
Robin Getz | 9d9b8fb0 | 2009-06-17 16:25:54 -0700 | [diff] [blame] | 38 | What: IRQF_SAMPLE_RANDOM |
| 39 | Check: IRQF_SAMPLE_RANDOM |
| 40 | When: July 2009 |
| 41 | |
| 42 | Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy |
| 43 | sources in the kernel's current entropy model. To resolve this, every |
| 44 | input point to the kernel's entropy pool needs to better document the |
| 45 | type of entropy source it actually is. This will be replaced with |
| 46 | additional add_*_randomness functions in drivers/char/random.c |
| 47 | |
| 48 | Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com> |
| 49 | |
| 50 | --------------------------- |
| 51 | |
Luis R. Rodriguez | 6ee7d33 | 2009-03-20 23:53:06 -0400 | [diff] [blame] | 52 | What: The ieee80211_regdom module parameter |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 53 | When: March 2010 / desktop catchup |
Luis R. Rodriguez | 6ee7d33 | 2009-03-20 23:53:06 -0400 | [diff] [blame] | 54 | |
| 55 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, |
| 56 | and currently serves as an option for users to define an |
| 57 | ISO / IEC 3166 alpha2 code for the country they are currently |
| 58 | present in. Although there are userspace API replacements for this |
| 59 | through nl80211 distributions haven't yet caught up with implementing |
| 60 | decent alternatives through standard GUIs. Although available as an |
| 61 | option through iw or wpa_supplicant its just a matter of time before |
| 62 | distributions pick up good GUI options for this. The ideal solution |
| 63 | would actually consist of intelligent designs which would do this for |
| 64 | the user automatically even when travelling through different countries. |
| 65 | Until then we leave this module parameter as a compromise. |
| 66 | |
| 67 | When userspace improves with reasonable widely-available alternatives for |
| 68 | this we will no longer need this module parameter. This entry hopes that |
| 69 | by the super-futuristically looking date of "March 2010" we will have |
| 70 | such replacements widely available. |
| 71 | |
| 72 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 73 | |
| 74 | --------------------------- |
| 75 | |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 76 | What: CONFIG_WIRELESS_OLD_REGULATORY - old static regulatory information |
| 77 | When: March 2010 / desktop catchup |
| 78 | |
Luis R. Rodriguez | b2e1b30 | 2008-09-09 23:19:48 -0700 | [diff] [blame] | 79 | Why: The old regulatory infrastructure has been replaced with a new one |
| 80 | which does not require statically defined regulatory domains. We do |
| 81 | not want to keep static regulatory domains in the kernel due to the |
| 82 | the dynamic nature of regulatory law and localization. We kept around |
| 83 | the old static definitions for the regulatory domains of: |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 84 | |
Luis R. Rodriguez | b2e1b30 | 2008-09-09 23:19:48 -0700 | [diff] [blame] | 85 | * US |
| 86 | * JP |
| 87 | * EU |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 88 | |
Luis R. Rodriguez | b2e1b30 | 2008-09-09 23:19:48 -0700 | [diff] [blame] | 89 | and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 90 | set. We will remove this option once the standard Linux desktop catches |
| 91 | up with the new userspace APIs we have implemented. |
| 92 | |
Luis R. Rodriguez | b2e1b30 | 2008-09-09 23:19:48 -0700 | [diff] [blame] | 93 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 94 | |
| 95 | --------------------------- |
| 96 | |
Alan Stern | 471d055 | 2007-07-12 16:55:07 -0400 | [diff] [blame] | 97 | What: dev->power.power_state |
Pavel Machek | 1ebfd79 | 2006-08-30 13:50:27 -0700 | [diff] [blame] | 98 | When: July 2007 |
| 99 | Why: Broken design for runtime control over driver power states, confusing |
| 100 | driver-internal runtime power management with: mechanisms to support |
| 101 | system-wide sleep state transitions; event codes that distinguish |
| 102 | different phases of swsusp "sleep" transitions; and userspace policy |
| 103 | inputs. This framework was never widely used, and most attempts to |
| 104 | use it were broken. Drivers should instead be exposing domain-specific |
| 105 | interfaces either to kernel or to userspace. |
| 106 | Who: Pavel Machek <pavel@suse.cz> |
| 107 | |
| 108 | --------------------------- |
| 109 | |
Mauro Carvalho Chehab | 42d12f5 | 2009-03-10 05:02:28 -0300 | [diff] [blame] | 110 | What: Video4Linux API 1 ioctls and from Video devices. |
| 111 | When: July 2009 |
| 112 | Files: include/linux/videodev.h |
| 113 | Check: include/linux/videodev.h |
Mauro Carvalho Chehab | 11a5a10 | 2007-10-17 15:32:36 -0200 | [diff] [blame] | 114 | Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6 |
Mauro Carvalho Chehab | 875c296 | 2005-11-08 21:38:53 -0800 | [diff] [blame] | 115 | series. The old API have lots of drawbacks and don't provide enough |
| 116 | means to work with all video and audio standards. The newer API is |
| 117 | already available on the main drivers and should be used instead. |
| 118 | Newer drivers should use v4l_compat_translate_ioctl function to handle |
| 119 | old calls, replacing to newer ones. |
| 120 | Decoder iocts are using internally to allow video drivers to |
| 121 | communicate with video decoders. This should also be improved to allow |
| 122 | V4L2 calls being translated into compatible internal ioctls. |
Mauro Carvalho Chehab | 11a5a10 | 2007-10-17 15:32:36 -0200 | [diff] [blame] | 123 | Compatibility ioctls will be provided, for a while, via |
| 124 | v4l1-compat module. |
| 125 | Who: Mauro Carvalho Chehab <mchehab@infradead.org> |
Mauro Carvalho Chehab | 875c296 | 2005-11-08 21:38:53 -0800 | [diff] [blame] | 126 | |
| 127 | --------------------------- |
| 128 | |
Dominik Brodowski | bf45d9b0 | 2005-07-07 17:58:58 -0700 | [diff] [blame] | 129 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
| 130 | When: November 2005 |
| 131 | Files: drivers/pcmcia/: pcmcia_ioctl.c |
| 132 | Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a |
| 133 | normal hotpluggable bus, and with it using the default kernel |
| 134 | infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA |
| 135 | control ioctl needed by cardmgr and cardctl from pcmcia-cs is |
| 136 | unnecessary, and makes further cleanups and integration of the |
| 137 | PCMCIA subsystem into the Linux kernel device driver model more |
| 138 | difficult. The features provided by cardmgr and cardctl are either |
| 139 | handled by the kernel itself now or are available in the new |
| 140 | pcmciautils package available at |
| 141 | http://kernel.org/pub/linux/utils/kernel/pcmcia/ |
| 142 | Who: Dominik Brodowski <linux@brodo.de> |
Harald Welte | 7af4cc3 | 2005-08-09 19:44:15 -0700 | [diff] [blame] | 143 | |
| 144 | --------------------------- |
| 145 | |
Eric W. Biederman | 7058cb0 | 2007-10-18 03:05:58 -0700 | [diff] [blame] | 146 | What: sys_sysctl |
| 147 | When: September 2010 |
| 148 | Option: CONFIG_SYSCTL_SYSCALL |
| 149 | Why: The same information is available in a more convenient from |
| 150 | /proc/sys, and none of the sysctl variables appear to be |
| 151 | important performance wise. |
| 152 | |
| 153 | Binary sysctls are a long standing source of subtle kernel |
| 154 | bugs and security issues. |
| 155 | |
| 156 | When I looked several months ago all I could find after |
| 157 | searching several distributions were 5 user space programs and |
| 158 | glibc (which falls back to /proc/sys) using this syscall. |
| 159 | |
| 160 | The man page for sysctl(2) documents it as unusable for user |
| 161 | space programs. |
| 162 | |
| 163 | sysctl(2) is not generally ABI compatible to a 32bit user |
| 164 | space application on a 64bit and a 32bit kernel. |
| 165 | |
| 166 | For the last several months the policy has been no new binary |
| 167 | sysctls and no one has put forward an argument to use them. |
| 168 | |
| 169 | Binary sysctls issues seem to keep happening appearing so |
| 170 | properly deprecating them (with a warning to user space) and a |
| 171 | 2 year grace warning period will mean eventually we can kill |
| 172 | them and end the pain. |
| 173 | |
| 174 | In the mean time individual binary sysctls can be dealt with |
| 175 | in a piecewise fashion. |
| 176 | |
| 177 | Who: Eric Biederman <ebiederm@xmission.com> |
| 178 | |
| 179 | --------------------------- |
| 180 | |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 181 | What: remove EXPORT_SYMBOL(kernel_thread) |
| 182 | When: August 2006 |
| 183 | Files: arch/*/kernel/*_ksyms.c |
Andy Whitcroft | f0a594c | 2007-07-19 01:48:34 -0700 | [diff] [blame] | 184 | Check: kernel_thread |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 185 | Why: kernel_thread is a low-level implementation detail. Drivers should |
| 186 | use the <linux/kthread.h> API instead which shields them from |
| 187 | implementation details and provides a higherlevel interface that |
| 188 | prevents bugs and code duplication |
| 189 | Who: Christoph Hellwig <hch@lst.de> |
| 190 | |
| 191 | --------------------------- |
| 192 | |
Arjan van de Ven | f71d20e | 2006-06-28 04:26:45 -0700 | [diff] [blame] | 193 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
| 194 | (temporary transition config option provided until then) |
| 195 | The transition config option will also be removed at the same time. |
| 196 | When: before 2.6.19 |
| 197 | Why: Unused symbols are both increasing the size of the kernel binary |
| 198 | and are often a sign of "wrong API" |
| 199 | Who: Arjan van de Ven <arjan@linux.intel.com> |
| 200 | |
| 201 | --------------------------- |
| 202 | |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 203 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment |
Dominik Brodowski | acbd39f | 2006-09-30 22:41:43 -0400 | [diff] [blame] | 204 | When: October 2008 |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 205 | Why: The stacking of class devices makes these values misleading and |
| 206 | inconsistent. |
| 207 | Class devices should not carry any of these properties, and bus |
| 208 | devices have SUBSYTEM and DRIVER as a replacement. |
| 209 | Who: Kay Sievers <kay.sievers@suse.de> |
| 210 | |
| 211 | --------------------------- |
Jean Delvare | 6c805d2 | 2006-08-13 23:45:52 +0200 | [diff] [blame] | 212 | |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 213 | What: ACPI procfs interface |
Zhang Rui | 8b8eb7d | 2007-07-18 17:23:24 +0800 | [diff] [blame] | 214 | When: July 2008 |
| 215 | Why: ACPI sysfs conversion should be finished by January 2008. |
| 216 | ACPI procfs interface will be removed in July 2008 so that |
| 217 | there is enough time for the user space to catch up. |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 218 | Who: Zhang Rui <rui.zhang@intel.com> |
| 219 | |
| 220 | --------------------------- |
| 221 | |
Len Brown | 1bb67c2 | 2007-01-11 01:49:44 -0500 | [diff] [blame] | 222 | What: /proc/acpi/button |
| 223 | When: August 2007 |
| 224 | Why: /proc/acpi/button has been replaced by events to the input layer |
| 225 | since 2.6.20. |
| 226 | Who: Len Brown <len.brown@intel.com> |
| 227 | |
| 228 | --------------------------- |
Jeff Garzik | 54b290a | 2007-01-23 00:29:01 -0500 | [diff] [blame] | 229 | |
Len Brown | 14e04fb3 | 2007-08-23 15:20:26 -0400 | [diff] [blame] | 230 | What: /proc/acpi/event |
| 231 | When: February 2008 |
| 232 | Why: /proc/acpi/event has been replaced by events via the input layer |
| 233 | and netlink since 2.6.23. |
| 234 | Who: Len Brown <len.brown@intel.com> |
| 235 | |
| 236 | --------------------------- |
| 237 | |
Thomas Gleixner | 914d97f | 2007-10-11 11:20:05 +0200 | [diff] [blame] | 238 | What: i386/x86_64 bzImage symlinks |
Ingo Molnar | 19b4e7f | 2008-04-10 10:12:27 +0200 | [diff] [blame] | 239 | When: April 2010 |
Thomas Gleixner | 914d97f | 2007-10-11 11:20:05 +0200 | [diff] [blame] | 240 | |
| 241 | Why: The i386/x86_64 merge provides a symlink to the old bzImage |
| 242 | location so not yet updated user space tools, e.g. package |
| 243 | scripts, do not break. |
| 244 | Who: Thomas Gleixner <tglx@linutronix.de> |
Linus Torvalds | 038a500 | 2007-10-11 19:40:14 -0700 | [diff] [blame] | 245 | |
| 246 | --------------------------- |
| 247 | |
Jan Engelhardt | f9ef8a2 | 2008-01-14 23:43:34 -0800 | [diff] [blame] | 248 | What (Why): |
Jan Engelhardt | 079aa88 | 2008-10-08 11:35:00 +0200 | [diff] [blame] | 249 | - xt_recent: the old ipt_recent proc dir |
| 250 | (superseded by /proc/net/xt_recent) |
| 251 | |
Jan Engelhardt | f9ef8a2 | 2008-01-14 23:43:34 -0800 | [diff] [blame] | 252 | When: January 2009 or Linux 2.7.0, whichever comes first |
| 253 | Why: Superseded by newer revisions or modules |
| 254 | Who: Jan Engelhardt <jengelh@computergmbh.de> |
Michael Buesch | eb189d8b | 2008-01-28 14:47:41 -0800 | [diff] [blame] | 255 | |
| 256 | --------------------------- |
| 257 | |
David Brownell | 8a0cecf | 2009-04-02 16:57:06 -0700 | [diff] [blame] | 258 | What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib |
| 259 | When: February 2010 |
| 260 | Why: All callers should use explicit gpio_request()/gpio_free(). |
| 261 | The autorequest mechanism in gpiolib was provided mostly as a |
| 262 | migration aid for legacy GPIO interfaces (for SOC based GPIOs). |
| 263 | Those users have now largely migrated. Platforms implementing |
| 264 | the GPIO interfaces without using gpiolib will see no changes. |
| 265 | Who: David Brownell <dbrownell@users.sourceforge.net> |
| 266 | --------------------------- |
| 267 | |
Michael Buesch | eb189d8b | 2008-01-28 14:47:41 -0800 | [diff] [blame] | 268 | What: b43 support for firmware revision < 410 |
Michael Buesch | c557289 | 2008-12-27 18:26:39 +0100 | [diff] [blame] | 269 | When: The schedule was July 2008, but it was decided that we are going to keep the |
| 270 | code as long as there are no major maintanance headaches. |
| 271 | So it _could_ be removed _any_ time now, if it conflicts with something new. |
Michael Buesch | eb189d8b | 2008-01-28 14:47:41 -0800 | [diff] [blame] | 272 | Why: The support code for the old firmware hurts code readability/maintainability |
| 273 | and slightly hurts runtime performance. Bugfixes for the old firmware |
| 274 | are not provided by Broadcom anymore. |
| 275 | Who: Michael Buesch <mb@bu3sch.de> |
David S. Miller | e88bb41 | 2008-02-09 23:08:53 -0800 | [diff] [blame] | 276 | |
| 277 | --------------------------- |
| 278 | |
Glauber Costa | fae9a0d | 2008-04-08 13:20:56 -0300 | [diff] [blame] | 279 | What: usedac i386 kernel parameter |
| 280 | When: 2.6.27 |
| 281 | Why: replaced by allowdac and no dac combination |
| 282 | Who: Glauber Costa <gcosta@redhat.com> |
| 283 | |
Mark Fasheh | 52f7c21 | 2008-01-29 17:08:26 -0800 | [diff] [blame] | 284 | --------------------------- |
| 285 | |
Bjorn Helgaas | c80cfb0 | 2008-10-15 22:01:35 -0700 | [diff] [blame] | 286 | What: print_fn_descriptor_symbol() |
| 287 | When: October 2009 |
| 288 | Why: The %pF vsprintf format provides the same functionality in a |
| 289 | simpler way. print_fn_descriptor_symbol() is deprecated but |
| 290 | still present to give out-of-tree modules time to change. |
| 291 | Who: Bjorn Helgaas <bjorn.helgaas@hp.com> |
| 292 | |
| 293 | --------------------------- |
| 294 | |
Mark Fasheh | 52f7c21 | 2008-01-29 17:08:26 -0800 | [diff] [blame] | 295 | What: /sys/o2cb symlink |
| 296 | When: January 2010 |
| 297 | Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb |
| 298 | exists as a symlink for backwards compatibility for old versions of |
| 299 | ocfs2-tools. 2 years should be sufficient time to phase in new versions |
| 300 | which know to look in /sys/fs/o2cb. |
| 301 | Who: ocfs2-devel@oss.oracle.com |
Matthew Wilcox | d2f5e80 | 2008-04-19 13:49:34 -0400 | [diff] [blame] | 302 | |
| 303 | --------------------------- |
| 304 | |
Vlad Yasevich | ecbed6a | 2008-07-01 20:06:22 -0700 | [diff] [blame] | 305 | What: SCTP_GET_PEER_ADDRS_NUM_OLD, SCTP_GET_PEER_ADDRS_OLD, |
| 306 | SCTP_GET_LOCAL_ADDRS_NUM_OLD, SCTP_GET_LOCAL_ADDRS_OLD |
| 307 | When: June 2009 |
| 308 | Why: A newer version of the options have been introduced in 2005 that |
| 309 | removes the limitions of the old API. The sctp library has been |
| 310 | converted to use these new options at the same time. Any user |
| 311 | space app that directly uses the old options should convert to using |
| 312 | the new options. |
| 313 | Who: Vlad Yasevich <vladislav.yasevich@hp.com> |
David S. Miller | ea2aca0 | 2008-07-05 23:08:07 -0700 | [diff] [blame] | 314 | |
| 315 | --------------------------- |
| 316 | |
Ravikiran G Thirumalai | 2584e51 | 2009-03-31 15:21:26 -0700 | [diff] [blame] | 317 | What: Ability for non root users to shm_get hugetlb pages based on mlock |
| 318 | resource limits |
| 319 | When: 2.6.31 |
| 320 | Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or |
| 321 | have CAP_IPC_LOCK to be able to allocate shm segments backed by |
| 322 | huge pages. The mlock based rlimit check to allow shm hugetlb is |
| 323 | inconsistent with mmap based allocations. Hence it is being |
| 324 | deprecated. |
| 325 | Who: Ravikiran Thirumalai <kiran@scalex86.org> |
| 326 | |
| 327 | --------------------------- |
| 328 | |
Rene Herman | 16d7523 | 2008-06-24 19:38:56 +0200 | [diff] [blame] | 329 | What: CONFIG_THERMAL_HWMON |
| 330 | When: January 2009 |
| 331 | Why: This option was introduced just to allow older lm-sensors userspace |
| 332 | to keep working over the upgrade to 2.6.26. At the scheduled time of |
| 333 | removal fixed lm-sensors (2.x or 3.x) should be readily available. |
| 334 | Who: Rene Herman <rene.herman@gmail.com> |
Johannes Berg | 22bb1be | 2008-07-10 11:16:47 +0200 | [diff] [blame] | 335 | |
| 336 | --------------------------- |
| 337 | |
| 338 | What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS |
| 339 | (in net/core/net-sysfs.c) |
| 340 | When: After the only user (hal) has seen a release with the patches |
| 341 | for enough time, probably some time in 2010. |
| 342 | Why: Over 1K .text/.data size reduction, data is available in other |
| 343 | ways (ioctls) |
| 344 | Who: Johannes Berg <johannes@sipsolutions.net> |
Krzysztof Piotr Oledzki | 5840157 | 2008-07-21 10:01:34 -0700 | [diff] [blame] | 345 | |
| 346 | --------------------------- |
| 347 | |
| 348 | What: CONFIG_NF_CT_ACCT |
| 349 | When: 2.6.29 |
| 350 | Why: Accounting can now be enabled/disabled without kernel recompilation. |
| 351 | Currently used only to set a default value for a feature that is also |
| 352 | controlled by a kernel/module/sysfs/sysctl parameter. |
| 353 | Who: Krzysztof Piotr Oledzki <ole@ans.pl> |
| 354 | |
FUJITA Tomonori | 46dfa04 | 2008-09-10 22:22:34 +0200 | [diff] [blame] | 355 | --------------------------- |
| 356 | |
Dave Jones | 753b7ae | 2009-03-09 15:14:37 -0400 | [diff] [blame] | 357 | What: sysfs ui for changing p4-clockmod parameters |
| 358 | When: September 2009 |
| 359 | Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and |
| 360 | e088e4c9cdb618675874becb91b2fd581ee707e6. |
| 361 | Removal is subject to fixing any remaining bugs in ACPI which may |
| 362 | cause the thermal throttling not to happen at the right time. |
| 363 | Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com> |
Thomas Gleixner | 0e57aa1 | 2009-03-13 14:34:05 +0100 | [diff] [blame] | 364 | |
| 365 | ----------------------------- |
| 366 | |
| 367 | What: __do_IRQ all in one fits nothing interrupt handler |
| 368 | When: 2.6.32 |
| 369 | Why: __do_IRQ was kept for easy migration to the type flow handlers. |
| 370 | More than two years of migration time is enough. |
| 371 | Who: Thomas Gleixner <tglx@linutronix.de> |
Thomas Gleixner | cb065c0 | 2009-03-13 14:40:27 +0100 | [diff] [blame] | 372 | |
| 373 | ----------------------------- |
| 374 | |
Alex Chiang | f110ca4 | 2009-03-20 14:56:56 -0600 | [diff] [blame] | 375 | What: fakephp and associated sysfs files in /sys/bus/pci/slots/ |
| 376 | When: 2011 |
| 377 | Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to |
| 378 | represent a machine's physical PCI slots. The change in semantics |
| 379 | had userspace implications, as the hotplug core no longer allowed |
| 380 | drivers to create multiple sysfs files per physical slot (required |
| 381 | for multi-function devices, e.g.). fakephp was seen as a developer's |
| 382 | tool only, and its interface changed. Too late, we learned that |
| 383 | there were some users of the fakephp interface. |
| 384 | |
| 385 | In 2.6.30, the original fakephp interface was restored. At the same |
| 386 | time, the PCI core gained the ability that fakephp provided, namely |
| 387 | function-level hot-remove and hot-add. |
| 388 | |
| 389 | Since the PCI core now provides the same functionality, exposed in: |
| 390 | |
| 391 | /sys/bus/pci/rescan |
| 392 | /sys/bus/pci/devices/.../remove |
| 393 | /sys/bus/pci/devices/.../rescan |
| 394 | |
| 395 | there is no functional reason to maintain fakephp as well. |
| 396 | |
| 397 | We will keep the existing module so that 'modprobe fakephp' will |
| 398 | present the old /sys/bus/pci/slots/... interface for compatibility, |
| 399 | but users are urged to migrate their applications to the API above. |
| 400 | |
| 401 | After a reasonable transition period, we will remove the legacy |
| 402 | fakephp interface. |
| 403 | Who: Alex Chiang <achiang@hp.com> |
Jean Delvare | 3f307fb | 2009-04-13 17:02:13 +0200 | [diff] [blame] | 404 | |
| 405 | --------------------------- |
| 406 | |
| 407 | What: i2c-voodoo3 driver |
| 408 | When: October 2009 |
| 409 | Why: Superseded by tdfxfb. I2C/DDC support used to live in a separate |
| 410 | driver but this caused driver conflicts. |
| 411 | Who: Jean Delvare <khali@linux-fr.org> |
| 412 | Krzysztof Helt <krzysztof.h1@wp.pl> |
Johannes Berg | c64fb01 | 2009-06-02 13:01:38 +0200 | [diff] [blame] | 413 | |
| 414 | --------------------------- |
| 415 | |
| 416 | What: CONFIG_RFKILL_INPUT |
| 417 | When: 2.6.33 |
| 418 | Why: Should be implemented in userspace, policy daemon. |
| 419 | Who: Johannes Berg <johannes@sipsolutions.net> |
David S. Miller | 9cbc1cb | 2009-06-15 03:02:23 -0700 | [diff] [blame] | 420 | |
Eric Paris | cdc321f | 2009-06-29 11:13:30 -0400 | [diff] [blame] | 421 | --------------------------- |
| 422 | |
| 423 | What: CONFIG_INOTIFY |
| 424 | When: 2.6.33 |
| 425 | Why: last user (audit) will be converted to the newer more generic |
| 426 | and more easily maintained fsnotify subsystem |
| 427 | Who: Eric Paris <eparis@redhat.com> |
| 428 | |
Andi Kleen | 45f458e | 2009-04-28 23:18:26 +0200 | [diff] [blame] | 429 | ---------------------------- |
| 430 | |
venkatesh.pallipadi@intel.com | 37c90e8 | 2009-07-02 17:08:31 -0700 | [diff] [blame] | 431 | What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be |
| 432 | exported interface anymore. |
| 433 | When: 2.6.33 |
| 434 | Why: cpu_policy_rwsem has a new cleaner definition making it local to |
| 435 | cpufreq core and contained inside cpufreq.c. Other dependent |
| 436 | drivers should not use it in order to safely avoid lockdep issues. |
| 437 | Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> |
Tejun Heo | 93fe448 | 2009-08-06 18:14:26 +0900 | [diff] [blame] | 438 | |
| 439 | ---------------------------- |
| 440 | |
| 441 | What: sound-slot/service-* module aliases and related clutters in |
| 442 | sound/sound_core.c |
| 443 | When: August 2010 |
| 444 | Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR |
| 445 | (14) and requests modules using custom sound-slot/service-* |
| 446 | module aliases. The only benefit of doing this is allowing |
| 447 | use of custom module aliases which might as well be considered |
| 448 | a bug at this point. This preemptive claiming prevents |
| 449 | alternative OSS implementations. |
| 450 | |
| 451 | Till the feature is removed, the kernel will be requesting |
| 452 | both sound-slot/service-* and the standard char-major-* module |
| 453 | aliases and allow turning off the pre-claiming selectively via |
| 454 | CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss |
| 455 | kernel parameter. |
| 456 | |
| 457 | After the transition phase is complete, both the custom module |
| 458 | aliases and switches to disable it will go away. This removal |
| 459 | will also allow making ALSA OSS emulation independent of |
| 460 | sound_core. The dependency will be broken then too. |
| 461 | Who: Tejun Heo <tj@kernel.org> |
Alok Kataria | d0153ca | 2009-09-29 10:25:24 -0700 | [diff] [blame] | 462 | |
| 463 | ---------------------------- |
| 464 | |
| 465 | What: Support for VMware's guest paravirtuliazation technique [VMI] will be |
| 466 | dropped. |
| 467 | When: 2.6.37 or earlier. |
| 468 | Why: With the recent innovations in CPU hardware acceleration technologies |
| 469 | from Intel and AMD, VMware ran a few experiments to compare these |
| 470 | techniques to guest paravirtualization technique on VMware's platform. |
| 471 | These hardware assisted virtualization techniques have outperformed the |
| 472 | performance benefits provided by VMI in most of the workloads. VMware |
| 473 | expects that these hardware features will be ubiquitous in a couple of |
| 474 | years, as a result, VMware has started a phased retirement of this |
| 475 | feature from the hypervisor. We will be removing this feature from the |
| 476 | Kernel too. Right now we are targeting 2.6.37 but can retire earlier if |
| 477 | technical reasons (read opportunity to remove major chunk of pvops) |
| 478 | arise. |
| 479 | |
| 480 | Please note that VMI has always been an optimization and non-VMI kernels |
| 481 | still work fine on VMware's platform. |
| 482 | Latest versions of VMware's product which support VMI are, |
| 483 | Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence |
| 484 | releases for these products will continue supporting VMI. |
| 485 | |
| 486 | For more details about VMI retirement take a look at this, |
| 487 | http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html |
| 488 | |
| 489 | Who: Alok N Kataria <akataria@vmware.com> |
| 490 | |
| 491 | ---------------------------- |