2005-04-17 06:20:36 +08:00
|
|
|
The following is a list of files and features that are going to be
|
|
|
|
|
removed in the kernel source tree. Every entry should contain what
|
|
|
|
|
exactly is going away, why it is happening, and who is going to be doing
|
|
|
|
|
the work. When the feature is removed from the kernel, it should also
|
|
|
|
|
be removed from this file.
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-06-18 07:25:54 +08:00
|
|
|
What: IRQF_SAMPLE_RANDOM
|
|
|
|
|
Check: IRQF_SAMPLE_RANDOM
|
|
|
|
|
When: July 2009
|
|
|
|
|
|
|
|
|
|
Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy
|
|
|
|
|
sources in the kernel's current entropy model. To resolve this, every
|
|
|
|
|
input point to the kernel's entropy pool needs to better document the
|
|
|
|
|
type of entropy source it actually is. This will be replaced with
|
|
|
|
|
additional add_*_randomness functions in drivers/char/random.c
|
|
|
|
|
|
|
|
|
|
Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-21 11:53:06 +08:00
|
|
|
What: The ieee80211_regdom module parameter
|
2009-03-25 09:21:07 +08:00
|
|
|
When: March 2010 / desktop catchup
|
2009-03-21 11:53:06 +08:00
|
|
|
|
|
|
|
|
Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code,
|
|
|
|
|
and currently serves as an option for users to define an
|
|
|
|
|
ISO / IEC 3166 alpha2 code for the country they are currently
|
|
|
|
|
present in. Although there are userspace API replacements for this
|
|
|
|
|
through nl80211 distributions haven't yet caught up with implementing
|
|
|
|
|
decent alternatives through standard GUIs. Although available as an
|
|
|
|
|
option through iw or wpa_supplicant its just a matter of time before
|
|
|
|
|
distributions pick up good GUI options for this. The ideal solution
|
|
|
|
|
would actually consist of intelligent designs which would do this for
|
|
|
|
|
the user automatically even when travelling through different countries.
|
|
|
|
|
Until then we leave this module parameter as a compromise.
|
|
|
|
|
|
|
|
|
|
When userspace improves with reasonable widely-available alternatives for
|
|
|
|
|
this we will no longer need this module parameter. This entry hopes that
|
|
|
|
|
by the super-futuristically looking date of "March 2010" we will have
|
|
|
|
|
such replacements widely available.
|
|
|
|
|
|
|
|
|
|
Who: Luis R. Rodriguez <lrodriguez@atheros.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-25 09:21:07 +08:00
|
|
|
What: CONFIG_WIRELESS_OLD_REGULATORY - old static regulatory information
|
|
|
|
|
When: March 2010 / desktop catchup
|
|
|
|
|
|
2008-09-10 14:19:48 +08:00
|
|
|
Why: The old regulatory infrastructure has been replaced with a new one
|
|
|
|
|
which does not require statically defined regulatory domains. We do
|
|
|
|
|
not want to keep static regulatory domains in the kernel due to the
|
|
|
|
|
the dynamic nature of regulatory law and localization. We kept around
|
|
|
|
|
the old static definitions for the regulatory domains of:
|
2009-03-25 09:21:07 +08:00
|
|
|
|
2008-09-10 14:19:48 +08:00
|
|
|
* US
|
|
|
|
|
* JP
|
|
|
|
|
* EU
|
2009-03-25 09:21:07 +08:00
|
|
|
|
2008-09-10 14:19:48 +08:00
|
|
|
and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was
|
2009-03-25 09:21:07 +08:00
|
|
|
set. We will remove this option once the standard Linux desktop catches
|
|
|
|
|
up with the new userspace APIs we have implemented.
|
|
|
|
|
|
2008-09-10 14:19:48 +08:00
|
|
|
Who: Luis R. Rodriguez <lrodriguez@atheros.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-07-13 04:55:07 +08:00
|
|
|
What: dev->power.power_state
|
2006-08-31 04:50:27 +08:00
|
|
|
When: July 2007
|
|
|
|
|
Why: Broken design for runtime control over driver power states, confusing
|
|
|
|
|
driver-internal runtime power management with: mechanisms to support
|
|
|
|
|
system-wide sleep state transitions; event codes that distinguish
|
|
|
|
|
different phases of swsusp "sleep" transitions; and userspace policy
|
|
|
|
|
inputs. This framework was never widely used, and most attempts to
|
|
|
|
|
use it were broken. Drivers should instead be exposing domain-specific
|
|
|
|
|
interfaces either to kernel or to userspace.
|
|
|
|
|
Who: Pavel Machek <pavel@suse.cz>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-10 16:02:28 +08:00
|
|
|
What: Video4Linux API 1 ioctls and from Video devices.
|
|
|
|
|
When: July 2009
|
|
|
|
|
Files: include/linux/videodev.h
|
|
|
|
|
Check: include/linux/videodev.h
|
2007-10-18 01:32:36 +08:00
|
|
|
Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6
|
2005-11-09 13:38:53 +08:00
|
|
|
series. The old API have lots of drawbacks and don't provide enough
|
|
|
|
|
means to work with all video and audio standards. The newer API is
|
|
|
|
|
already available on the main drivers and should be used instead.
|
|
|
|
|
Newer drivers should use v4l_compat_translate_ioctl function to handle
|
|
|
|
|
old calls, replacing to newer ones.
|
|
|
|
|
Decoder iocts are using internally to allow video drivers to
|
|
|
|
|
communicate with video decoders. This should also be improved to allow
|
|
|
|
|
V4L2 calls being translated into compatible internal ioctls.
|
2007-10-18 01:32:36 +08:00
|
|
|
Compatibility ioctls will be provided, for a while, via
|
|
|
|
|
v4l1-compat module.
|
|
|
|
|
Who: Mauro Carvalho Chehab <mchehab@infradead.org>
|
2005-11-09 13:38:53 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2005-07-08 08:58:58 +08:00
|
|
|
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
|
|
|
|
|
When: November 2005
|
|
|
|
|
Files: drivers/pcmcia/: pcmcia_ioctl.c
|
|
|
|
|
Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a
|
|
|
|
|
normal hotpluggable bus, and with it using the default kernel
|
|
|
|
|
infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA
|
|
|
|
|
control ioctl needed by cardmgr and cardctl from pcmcia-cs is
|
|
|
|
|
unnecessary, and makes further cleanups and integration of the
|
|
|
|
|
PCMCIA subsystem into the Linux kernel device driver model more
|
|
|
|
|
difficult. The features provided by cardmgr and cardctl are either
|
|
|
|
|
handled by the kernel itself now or are available in the new
|
|
|
|
|
pcmciautils package available at
|
|
|
|
|
http://kernel.org/pub/linux/utils/kernel/pcmcia/
|
|
|
|
|
Who: Dominik Brodowski <linux@brodo.de>
|
2005-08-10 10:44:15 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-10-18 18:05:58 +08:00
|
|
|
What: sys_sysctl
|
|
|
|
|
When: September 2010
|
|
|
|
|
Option: CONFIG_SYSCTL_SYSCALL
|
|
|
|
|
Why: The same information is available in a more convenient from
|
|
|
|
|
/proc/sys, and none of the sysctl variables appear to be
|
|
|
|
|
important performance wise.
|
|
|
|
|
|
|
|
|
|
Binary sysctls are a long standing source of subtle kernel
|
|
|
|
|
bugs and security issues.
|
|
|
|
|
|
|
|
|
|
When I looked several months ago all I could find after
|
|
|
|
|
searching several distributions were 5 user space programs and
|
|
|
|
|
glibc (which falls back to /proc/sys) using this syscall.
|
|
|
|
|
|
|
|
|
|
The man page for sysctl(2) documents it as unusable for user
|
|
|
|
|
space programs.
|
|
|
|
|
|
|
|
|
|
sysctl(2) is not generally ABI compatible to a 32bit user
|
|
|
|
|
space application on a 64bit and a 32bit kernel.
|
|
|
|
|
|
|
|
|
|
For the last several months the policy has been no new binary
|
|
|
|
|
sysctls and no one has put forward an argument to use them.
|
|
|
|
|
|
|
|
|
|
Binary sysctls issues seem to keep happening appearing so
|
|
|
|
|
properly deprecating them (with a warning to user space) and a
|
|
|
|
|
2 year grace warning period will mean eventually we can kill
|
|
|
|
|
them and end the pain.
|
|
|
|
|
|
|
|
|
|
In the mean time individual binary sysctls can be dealt with
|
|
|
|
|
in a piecewise fashion.
|
|
|
|
|
|
|
|
|
|
Who: Eric Biederman <ebiederm@xmission.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-03-24 19:18:22 +08:00
|
|
|
What: remove EXPORT_SYMBOL(kernel_thread)
|
|
|
|
|
When: August 2006
|
|
|
|
|
Files: arch/*/kernel/*_ksyms.c
|
2007-07-19 16:48:34 +08:00
|
|
|
Check: kernel_thread
|
2006-03-24 19:18:22 +08:00
|
|
|
Why: kernel_thread is a low-level implementation detail. Drivers should
|
|
|
|
|
use the <linux/kthread.h> API instead which shields them from
|
|
|
|
|
implementation details and provides a higherlevel interface that
|
|
|
|
|
prevents bugs and code duplication
|
|
|
|
|
Who: Christoph Hellwig <hch@lst.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-06-28 19:26:45 +08:00
|
|
|
What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
|
|
|
|
|
(temporary transition config option provided until then)
|
|
|
|
|
The transition config option will also be removed at the same time.
|
|
|
|
|
When: before 2.6.19
|
|
|
|
|
Why: Unused symbols are both increasing the size of the kernel binary
|
|
|
|
|
and are often a sign of "wrong API"
|
|
|
|
|
Who: Arjan van de Ven <arjan@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-08-13 12:17:09 +08:00
|
|
|
What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
|
2006-10-01 10:41:43 +08:00
|
|
|
When: October 2008
|
2006-08-13 12:17:09 +08:00
|
|
|
Why: The stacking of class devices makes these values misleading and
|
|
|
|
|
inconsistent.
|
|
|
|
|
Class devices should not carry any of these properties, and bus
|
|
|
|
|
devices have SUBSYTEM and DRIVER as a replacement.
|
|
|
|
|
Who: Kay Sievers <kay.sievers@suse.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2006-08-14 05:45:52 +08:00
|
|
|
|
2007-01-29 11:02:30 +08:00
|
|
|
What: ACPI procfs interface
|
2007-07-18 17:23:24 +08:00
|
|
|
When: July 2008
|
|
|
|
|
Why: ACPI sysfs conversion should be finished by January 2008.
|
|
|
|
|
ACPI procfs interface will be removed in July 2008 so that
|
|
|
|
|
there is enough time for the user space to catch up.
|
2007-01-29 11:02:30 +08:00
|
|
|
Who: Zhang Rui <rui.zhang@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-01-11 14:49:44 +08:00
|
|
|
What: /proc/acpi/button
|
|
|
|
|
When: August 2007
|
|
|
|
|
Why: /proc/acpi/button has been replaced by events to the input layer
|
|
|
|
|
since 2.6.20.
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2007-01-23 13:29:01 +08:00
|
|
|
|
2007-08-24 03:20:26 +08:00
|
|
|
What: /proc/acpi/event
|
|
|
|
|
When: February 2008
|
|
|
|
|
Why: /proc/acpi/event has been replaced by events via the input layer
|
|
|
|
|
and netlink since 2.6.23.
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-05-17 22:43:26 +08:00
|
|
|
What: libata spindown skipping and warning
|
libata: implement libata.spindown_compat
Now that libata uses sd->manage_start_stop, libata spins down disk on
shutdown. In an attempt to compensate libata's previous shortcoming,
some distros sync and spin down disks attached via libata in their
shutdown(8). Some disks spin back up just to spin down again on
STANDBYNOW1 if the command is issued when the disk is spun down, so
this double spinning down causes problem.
This patch implements module parameter libata.spindown_compat which,
when set to one (default value), prevents libata from spinning down
disks on shutdown thus avoiding double spinning down. Note that
libata spins down disks for suspend to mem and disk, so with
libata.spindown_compat set to one, disks should be properly spun down
in all cases without modifying shutdown(8).
shutdown(8) should be fixed eventually. Some drive do spin up on
SYNCHRONZE_CACHE even when their cache is clean. Those disks
currently spin up briefly when sd tries to shutdown the device and
then the machine powers off immediately, which can't be good for the
head. We can't skip SYNCHRONIZE_CACHE during shudown as it can be
dangerous data integrity-wise.
So, this spindown_compat parameter is already scheduled for removal by
the end of the next year and here's what shutdown(8) should do.
* Check whether /sys/modules/libata/parameters/spindown_compat
exists. If it does, write 0 to it.
* For each libata harddisk {
* Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop
exists. Iff it doesn't, synchronize cache and spin the disk
down as before.
}
The above procedure will make shutdown(8) work properly with kernels
before this change, ones with this workaround and later ones without
it.
To accelerate shutdown(8) updates, if the compat mode is in use, this
patch prints BIG FAT warning for five seconds during shutdown (the
optimal interval to annoy the user just the right amount discovered by
hours of tireless usability testing).
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-05-05 03:28:48 +08:00
|
|
|
When: Dec 2008
|
2007-05-17 22:43:26 +08:00
|
|
|
Why: Some halt(8) implementations synchronize caches for and spin
|
|
|
|
|
down libata disks because libata didn't use to spin down disk on
|
|
|
|
|
system halt (only synchronized caches).
|
|
|
|
|
Spin down on system halt is now implemented. sysfs node
|
|
|
|
|
/sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if
|
|
|
|
|
spin down support is available.
|
libata: implement libata.spindown_compat
Now that libata uses sd->manage_start_stop, libata spins down disk on
shutdown. In an attempt to compensate libata's previous shortcoming,
some distros sync and spin down disks attached via libata in their
shutdown(8). Some disks spin back up just to spin down again on
STANDBYNOW1 if the command is issued when the disk is spun down, so
this double spinning down causes problem.
This patch implements module parameter libata.spindown_compat which,
when set to one (default value), prevents libata from spinning down
disks on shutdown thus avoiding double spinning down. Note that
libata spins down disks for suspend to mem and disk, so with
libata.spindown_compat set to one, disks should be properly spun down
in all cases without modifying shutdown(8).
shutdown(8) should be fixed eventually. Some drive do spin up on
SYNCHRONZE_CACHE even when their cache is clean. Those disks
currently spin up briefly when sd tries to shutdown the device and
then the machine powers off immediately, which can't be good for the
head. We can't skip SYNCHRONIZE_CACHE during shudown as it can be
dangerous data integrity-wise.
So, this spindown_compat parameter is already scheduled for removal by
the end of the next year and here's what shutdown(8) should do.
* Check whether /sys/modules/libata/parameters/spindown_compat
exists. If it does, write 0 to it.
* For each libata harddisk {
* Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop
exists. Iff it doesn't, synchronize cache and spin the disk
down as before.
}
The above procedure will make shutdown(8) work properly with kernels
before this change, ones with this workaround and later ones without
it.
To accelerate shutdown(8) updates, if the compat mode is in use, this
patch prints BIG FAT warning for five seconds during shutdown (the
optimal interval to annoy the user just the right amount discovered by
hours of tireless usability testing).
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-05-05 03:28:48 +08:00
|
|
|
Because issuing spin down command to an already spun down disk
|
2007-05-17 22:43:26 +08:00
|
|
|
makes some disks spin up just to spin down again, libata tracks
|
|
|
|
|
device spindown status to skip the extra spindown command and
|
|
|
|
|
warn about it.
|
|
|
|
|
This is to give userspace tools the time to get updated and will
|
|
|
|
|
be removed after userspace is reasonably updated.
|
libata: implement libata.spindown_compat
Now that libata uses sd->manage_start_stop, libata spins down disk on
shutdown. In an attempt to compensate libata's previous shortcoming,
some distros sync and spin down disks attached via libata in their
shutdown(8). Some disks spin back up just to spin down again on
STANDBYNOW1 if the command is issued when the disk is spun down, so
this double spinning down causes problem.
This patch implements module parameter libata.spindown_compat which,
when set to one (default value), prevents libata from spinning down
disks on shutdown thus avoiding double spinning down. Note that
libata spins down disks for suspend to mem and disk, so with
libata.spindown_compat set to one, disks should be properly spun down
in all cases without modifying shutdown(8).
shutdown(8) should be fixed eventually. Some drive do spin up on
SYNCHRONZE_CACHE even when their cache is clean. Those disks
currently spin up briefly when sd tries to shutdown the device and
then the machine powers off immediately, which can't be good for the
head. We can't skip SYNCHRONIZE_CACHE during shudown as it can be
dangerous data integrity-wise.
So, this spindown_compat parameter is already scheduled for removal by
the end of the next year and here's what shutdown(8) should do.
* Check whether /sys/modules/libata/parameters/spindown_compat
exists. If it does, write 0 to it.
* For each libata harddisk {
* Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop
exists. Iff it doesn't, synchronize cache and spin the disk
down as before.
}
The above procedure will make shutdown(8) work properly with kernels
before this change, ones with this workaround and later ones without
it.
To accelerate shutdown(8) updates, if the compat mode is in use, this
patch prints BIG FAT warning for five seconds during shutdown (the
optimal interval to annoy the user just the right amount discovered by
hours of tireless usability testing).
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-05-05 03:28:48 +08:00
|
|
|
Who: Tejun Heo <htejun@gmail.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-10-11 17:20:05 +08:00
|
|
|
What: i386/x86_64 bzImage symlinks
|
2008-04-10 16:12:27 +08:00
|
|
|
When: April 2010
|
2007-10-11 17:20:05 +08:00
|
|
|
|
|
|
|
|
Why: The i386/x86_64 merge provides a symlink to the old bzImage
|
|
|
|
|
location so not yet updated user space tools, e.g. package
|
|
|
|
|
scripts, do not break.
|
|
|
|
|
Who: Thomas Gleixner <tglx@linutronix.de>
|
2007-10-12 10:40:14 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-01-15 15:43:34 +08:00
|
|
|
What (Why):
|
|
|
|
|
- include/linux/netfilter_ipv4/ipt_TOS.h ipt_tos.h header files
|
|
|
|
|
(superseded by xt_TOS/xt_tos target & match)
|
|
|
|
|
|
|
|
|
|
- "forwarding" header files like ipt_mac.h in
|
|
|
|
|
include/linux/netfilter_ipv4/ and include/linux/netfilter_ipv6/
|
|
|
|
|
|
|
|
|
|
- xt_CONNMARK match revision 0
|
|
|
|
|
(superseded by xt_CONNMARK match revision 1)
|
|
|
|
|
|
|
|
|
|
- xt_MARK target revisions 0 and 1
|
|
|
|
|
(superseded by xt_MARK match revision 2)
|
|
|
|
|
|
|
|
|
|
- xt_connmark match revision 0
|
|
|
|
|
(superseded by xt_connmark match revision 1)
|
|
|
|
|
|
|
|
|
|
- xt_conntrack match revision 0
|
|
|
|
|
(superseded by xt_conntrack match revision 1)
|
|
|
|
|
|
|
|
|
|
- xt_iprange match revision 0,
|
|
|
|
|
include/linux/netfilter_ipv4/ipt_iprange.h
|
|
|
|
|
(superseded by xt_iprange match revision 1)
|
|
|
|
|
|
|
|
|
|
- xt_mark match revision 0
|
|
|
|
|
(superseded by xt_mark match revision 1)
|
|
|
|
|
|
2008-10-08 17:35:00 +08:00
|
|
|
- xt_recent: the old ipt_recent proc dir
|
|
|
|
|
(superseded by /proc/net/xt_recent)
|
|
|
|
|
|
2008-01-15 15:43:34 +08:00
|
|
|
When: January 2009 or Linux 2.7.0, whichever comes first
|
|
|
|
|
Why: Superseded by newer revisions or modules
|
|
|
|
|
Who: Jan Engelhardt <jengelh@computergmbh.de>
|
2008-01-29 06:47:41 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-04-03 07:57:06 +08:00
|
|
|
What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib
|
|
|
|
|
When: February 2010
|
|
|
|
|
Why: All callers should use explicit gpio_request()/gpio_free().
|
|
|
|
|
The autorequest mechanism in gpiolib was provided mostly as a
|
|
|
|
|
migration aid for legacy GPIO interfaces (for SOC based GPIOs).
|
|
|
|
|
Those users have now largely migrated. Platforms implementing
|
|
|
|
|
the GPIO interfaces without using gpiolib will see no changes.
|
|
|
|
|
Who: David Brownell <dbrownell@users.sourceforge.net>
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-01-29 06:47:41 +08:00
|
|
|
What: b43 support for firmware revision < 410
|
2008-12-28 01:26:39 +08:00
|
|
|
When: The schedule was July 2008, but it was decided that we are going to keep the
|
|
|
|
|
code as long as there are no major maintanance headaches.
|
|
|
|
|
So it _could_ be removed _any_ time now, if it conflicts with something new.
|
2008-01-29 06:47:41 +08:00
|
|
|
Why: The support code for the old firmware hurts code readability/maintainability
|
|
|
|
|
and slightly hurts runtime performance. Bugfixes for the old firmware
|
|
|
|
|
are not provided by Broadcom anymore.
|
|
|
|
|
Who: Michael Buesch <mb@bu3sch.de>
|
2008-02-10 15:08:53 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-04-09 00:20:56 +08:00
|
|
|
What: usedac i386 kernel parameter
|
|
|
|
|
When: 2.6.27
|
|
|
|
|
Why: replaced by allowdac and no dac combination
|
|
|
|
|
Who: Glauber Costa <gcosta@redhat.com>
|
|
|
|
|
|
2008-01-30 09:08:26 +08:00
|
|
|
---------------------------
|
|
|
|
|
|
2008-10-16 13:01:35 +08:00
|
|
|
What: print_fn_descriptor_symbol()
|
|
|
|
|
When: October 2009
|
|
|
|
|
Why: The %pF vsprintf format provides the same functionality in a
|
|
|
|
|
simpler way. print_fn_descriptor_symbol() is deprecated but
|
|
|
|
|
still present to give out-of-tree modules time to change.
|
|
|
|
|
Who: Bjorn Helgaas <bjorn.helgaas@hp.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-01-30 09:08:26 +08:00
|
|
|
What: /sys/o2cb symlink
|
|
|
|
|
When: January 2010
|
|
|
|
|
Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb
|
|
|
|
|
exists as a symlink for backwards compatibility for old versions of
|
|
|
|
|
ocfs2-tools. 2 years should be sufficient time to phase in new versions
|
|
|
|
|
which know to look in /sys/fs/o2cb.
|
|
|
|
|
Who: ocfs2-devel@oss.oracle.com
|
2008-04-20 01:49:34 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-07-02 11:06:22 +08:00
|
|
|
What: SCTP_GET_PEER_ADDRS_NUM_OLD, SCTP_GET_PEER_ADDRS_OLD,
|
|
|
|
|
SCTP_GET_LOCAL_ADDRS_NUM_OLD, SCTP_GET_LOCAL_ADDRS_OLD
|
|
|
|
|
When: June 2009
|
|
|
|
|
Why: A newer version of the options have been introduced in 2005 that
|
|
|
|
|
removes the limitions of the old API. The sctp library has been
|
|
|
|
|
converted to use these new options at the same time. Any user
|
|
|
|
|
space app that directly uses the old options should convert to using
|
|
|
|
|
the new options.
|
|
|
|
|
Who: Vlad Yasevich <vladislav.yasevich@hp.com>
|
2008-07-06 14:08:07 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-04-01 06:21:26 +08:00
|
|
|
What: Ability for non root users to shm_get hugetlb pages based on mlock
|
|
|
|
|
resource limits
|
|
|
|
|
When: 2.6.31
|
|
|
|
|
Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or
|
|
|
|
|
have CAP_IPC_LOCK to be able to allocate shm segments backed by
|
|
|
|
|
huge pages. The mlock based rlimit check to allow shm hugetlb is
|
|
|
|
|
inconsistent with mmap based allocations. Hence it is being
|
|
|
|
|
deprecated.
|
|
|
|
|
Who: Ravikiran Thirumalai <kiran@scalex86.org>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2008-06-25 01:38:56 +08:00
|
|
|
What: CONFIG_THERMAL_HWMON
|
|
|
|
|
When: January 2009
|
|
|
|
|
Why: This option was introduced just to allow older lm-sensors userspace
|
|
|
|
|
to keep working over the upgrade to 2.6.26. At the scheduled time of
|
|
|
|
|
removal fixed lm-sensors (2.x or 3.x) should be readily available.
|
|
|
|
|
Who: Rene Herman <rene.herman@gmail.com>
|
2008-07-10 17:16:47 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
|
|
|
|
|
(in net/core/net-sysfs.c)
|
|
|
|
|
When: After the only user (hal) has seen a release with the patches
|
|
|
|
|
for enough time, probably some time in 2010.
|
|
|
|
|
Why: Over 1K .text/.data size reduction, data is available in other
|
|
|
|
|
ways (ioctls)
|
|
|
|
|
Who: Johannes Berg <johannes@sipsolutions.net>
|
netfilter: accounting rework: ct_extend + 64bit counters (v4)
Initially netfilter has had 64bit counters for conntrack-based accounting, but
it was changed in 2.6.14 to save memory. Unfortunately in-kernel 64bit counters are
still required, for example for "connbytes" extension. However, 64bit counters
waste a lot of memory and it was not possible to enable/disable it runtime.
This patch:
- reimplements accounting with respect to the extension infrastructure,
- makes one global version of seq_print_acct() instead of two seq_print_counters(),
- makes it possible to enable it at boot time (for CONFIG_SYSCTL/CONFIG_SYSFS=n),
- makes it possible to enable/disable it at runtime by sysctl or sysfs,
- extends counters from 32bit to 64bit,
- renames ip_conntrack_counter -> nf_conn_counter,
- enables accounting code unconditionally (no longer depends on CONFIG_NF_CT_ACCT),
- set initial accounting enable state based on CONFIG_NF_CT_ACCT
- removes buggy IPCT_COUNTER_FILLING event handling.
If accounting is enabled newly created connections get additional acct extend.
Old connections are not changed as it is not possible to add a ct_extend area
to confirmed conntrack. Accounting is performed for all connections with
acct extend regardless of a current state of "net.netfilter.nf_conntrack_acct".
Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2008-07-22 01:01:34 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: CONFIG_NF_CT_ACCT
|
|
|
|
|
When: 2.6.29
|
|
|
|
|
Why: Accounting can now be enabled/disabled without kernel recompilation.
|
|
|
|
|
Currently used only to set a default value for a feature that is also
|
|
|
|
|
controlled by a kernel/module/sysfs/sysctl parameter.
|
|
|
|
|
Who: Krzysztof Piotr Oledzki <ole@ans.pl>
|
|
|
|
|
|
2008-09-11 04:22:34 +08:00
|
|
|
---------------------------
|
|
|
|
|
|
2009-01-07 23:37:33 +08:00
|
|
|
What: fscher and fscpos drivers
|
|
|
|
|
When: June 2009
|
|
|
|
|
Why: Deprecated by the new fschmd driver.
|
|
|
|
|
Who: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-10 03:14:37 +08:00
|
|
|
What: sysfs ui for changing p4-clockmod parameters
|
|
|
|
|
When: September 2009
|
|
|
|
|
Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
|
|
|
|
|
e088e4c9cdb618675874becb91b2fd581ee707e6.
|
|
|
|
|
Removal is subject to fixing any remaining bugs in ACPI which may
|
|
|
|
|
cause the thermal throttling not to happen at the right time.
|
|
|
|
|
Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
|
2009-03-13 21:34:05 +08:00
|
|
|
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
|
|
|
|
What: __do_IRQ all in one fits nothing interrupt handler
|
|
|
|
|
When: 2.6.32
|
|
|
|
|
Why: __do_IRQ was kept for easy migration to the type flow handlers.
|
|
|
|
|
More than two years of migration time is enough.
|
|
|
|
|
Who: Thomas Gleixner <tglx@linutronix.de>
|
2009-03-13 21:40:27 +08:00
|
|
|
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
|
|
|
|
What: obsolete generic irq defines and typedefs
|
|
|
|
|
When: 2.6.30
|
|
|
|
|
Why: The defines and typedefs (hw_interrupt_type, no_irq_type, irq_desc_t)
|
|
|
|
|
have been kept around for migration reasons. After more than two years
|
|
|
|
|
it's time to remove them finally
|
|
|
|
|
Who: Thomas Gleixner <tglx@linutronix.de>
|
2009-04-02 00:47:12 +08:00
|
|
|
|
2009-03-21 04:56:56 +08:00
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: fakephp and associated sysfs files in /sys/bus/pci/slots/
|
|
|
|
|
When: 2011
|
|
|
|
|
Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
|
|
|
|
|
represent a machine's physical PCI slots. The change in semantics
|
|
|
|
|
had userspace implications, as the hotplug core no longer allowed
|
|
|
|
|
drivers to create multiple sysfs files per physical slot (required
|
|
|
|
|
for multi-function devices, e.g.). fakephp was seen as a developer's
|
|
|
|
|
tool only, and its interface changed. Too late, we learned that
|
|
|
|
|
there were some users of the fakephp interface.
|
|
|
|
|
|
|
|
|
|
In 2.6.30, the original fakephp interface was restored. At the same
|
|
|
|
|
time, the PCI core gained the ability that fakephp provided, namely
|
|
|
|
|
function-level hot-remove and hot-add.
|
|
|
|
|
|
|
|
|
|
Since the PCI core now provides the same functionality, exposed in:
|
|
|
|
|
|
|
|
|
|
/sys/bus/pci/rescan
|
|
|
|
|
/sys/bus/pci/devices/.../remove
|
|
|
|
|
/sys/bus/pci/devices/.../rescan
|
|
|
|
|
|
|
|
|
|
there is no functional reason to maintain fakephp as well.
|
|
|
|
|
|
|
|
|
|
We will keep the existing module so that 'modprobe fakephp' will
|
|
|
|
|
present the old /sys/bus/pci/slots/... interface for compatibility,
|
|
|
|
|
but users are urged to migrate their applications to the API above.
|
|
|
|
|
|
|
|
|
|
After a reasonable transition period, we will remove the legacy
|
|
|
|
|
fakephp interface.
|
|
|
|
|
Who: Alex Chiang <achiang@hp.com>
|
2009-04-13 23:02:13 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: i2c-voodoo3 driver
|
|
|
|
|
When: October 2009
|
|
|
|
|
Why: Superseded by tdfxfb. I2C/DDC support used to live in a separate
|
|
|
|
|
driver but this caused driver conflicts.
|
|
|
|
|
Who: Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
Krzysztof Helt <krzysztof.h1@wp.pl>
|
2009-06-02 19:01:38 +08:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: CONFIG_RFKILL_INPUT
|
|
|
|
|
When: 2.6.33
|
|
|
|
|
Why: Should be implemented in userspace, policy daemon.
|
|
|
|
|
Who: Johannes Berg <johannes@sipsolutions.net>
|
2009-06-15 18:02:23 +08:00
|
|
|
|
2009-04-29 05:18:26 +08:00
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: CONFIG_X86_OLD_MCE
|
|
|
|
|
When: 2.6.32
|
|
|
|
|
Why: Remove the old legacy 32bit machine check code. This has been
|
|
|
|
|
superseded by the newer machine check code from the 64bit port,
|
|
|
|
|
but the old version has been kept around for easier testing. Note this
|
|
|
|
|
doesn't impact the old P5 and WinChip machine check handlers.
|
|
|
|
|
Who: Andi Kleen <andi@firstfloor.org>
|
2009-07-03 08:08:31 +08:00
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be
|
|
|
|
|
exported interface anymore.
|
|
|
|
|
When: 2.6.33
|
|
|
|
|
Why: cpu_policy_rwsem has a new cleaner definition making it local to
|
|
|
|
|
cpufreq core and contained inside cpufreq.c. Other dependent
|
|
|
|
|
drivers should not use it in order to safely avoid lockdep issues.
|
|
|
|
|
Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
|