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