2005-04-16 22:20:36 +00: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.
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2011-04-01 19:08:48 +00:00
|
|
|
What: x86 floppy disable_hlt
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: ancient workaround of dubious utility clutters the
|
|
|
|
|
code used by everybody else.
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2011-04-01 19:19:23 +00:00
|
|
|
What: CONFIG_APM_CPU_IDLE, and its ability to call APM BIOS in idle
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: This optional sub-feature of APM is of dubious reliability,
|
|
|
|
|
and ancient APM laptops are likely better served by calling HLT.
|
|
|
|
|
Deleting CONFIG_APM_CPU_IDLE allows x86 to stop exporting
|
|
|
|
|
the pm_idle function pointer to modules.
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2011-04-01 19:41:17 +00:00
|
|
|
What: x86_32 "no-hlt" cmdline param
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: remove a branch from idle path, simplify code used by everybody.
|
|
|
|
|
This option disabled the use of HLT in idle and machine_halt()
|
|
|
|
|
for hardware that was flakey 15-years ago. Today we have
|
|
|
|
|
"idle=poll" that removed HLT from idle, and so if such a machine
|
|
|
|
|
is still running the upstream kernel, "idle=poll" is likely sufficient.
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2011-04-01 19:46:09 +00:00
|
|
|
What: x86 "idle=mwait" cmdline param
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: simplify x86 idle code
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2009-09-08 19:09:47 +00:00
|
|
|
What: PRISM54
|
|
|
|
|
When: 2.6.34
|
|
|
|
|
|
|
|
|
|
Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the
|
|
|
|
|
prism54 wireless driver. After Intersil stopped selling these
|
|
|
|
|
devices in preference for the newer more flexible SoftMAC devices
|
|
|
|
|
a SoftMAC device driver was required and prism54 did not support
|
|
|
|
|
them. The p54pci driver now exists and has been present in the kernel for
|
|
|
|
|
a while. This driver supports both SoftMAC devices and FullMAC devices.
|
|
|
|
|
The main difference between these devices was the amount of memory which
|
|
|
|
|
could be used for the firmware. The SoftMAC devices support a smaller
|
|
|
|
|
amount of memory. Because of this the SoftMAC firmware fits into FullMAC
|
|
|
|
|
devices's memory. p54pci supports not only PCI / Cardbus but also USB
|
|
|
|
|
and SPI. Since p54pci supports all devices prism54 supports
|
|
|
|
|
you will have a conflict. I'm not quite sure how distributions are
|
|
|
|
|
handling this conflict right now. prism54 was kept around due to
|
|
|
|
|
claims users may experience issues when using the SoftMAC driver.
|
|
|
|
|
Time has passed users have not reported issues. If you use prism54
|
|
|
|
|
and for whatever reason you cannot use p54pci please let us know!
|
|
|
|
|
E-mail us at: linux-wireless@vger.kernel.org
|
|
|
|
|
|
|
|
|
|
For more information see the p54 wiki page:
|
|
|
|
|
|
|
|
|
|
http://wireless.kernel.org/en/users/Drivers/p54
|
|
|
|
|
|
|
|
|
|
Who: Luis R. Rodriguez <lrodriguez@atheros.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-06-17 23:25:54 +00: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>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2010-01-27 22:47:50 +00:00
|
|
|
What: Deprecated snapshot ioctls
|
|
|
|
|
When: 2.6.36
|
|
|
|
|
|
|
|
|
|
Why: The ioctls in kernel/power/user.c were marked as deprecated long time
|
|
|
|
|
ago. Now they notify users about that so that they need to replace
|
|
|
|
|
their userspace. After some more time, remove them completely.
|
|
|
|
|
|
|
|
|
|
Who: Jiri Slaby <jirislaby@gmail.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-21 03:53:06 +00:00
|
|
|
What: The ieee80211_regdom module parameter
|
2009-03-25 01:21:07 +00:00
|
|
|
When: March 2010 / desktop catchup
|
2009-03-21 03:53:06 +00: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>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-07-12 20:55:07 +00:00
|
|
|
What: dev->power.power_state
|
2006-08-30 20:50:27 +00: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.
|
2010-07-18 12:27:13 +00:00
|
|
|
Who: Pavel Machek <pavel@ucw.cz>
|
2006-08-30 20:50:27 +00:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-10-18 10:05:58 +00: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>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2010-08-10 00:19:47 +00:00
|
|
|
What: /proc/<pid>/oom_adj
|
|
|
|
|
When: August 2012
|
|
|
|
|
Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's
|
|
|
|
|
badness heuristic used to determine which task to kill when the kernel
|
|
|
|
|
is out of memory.
|
|
|
|
|
|
|
|
|
|
The badness heuristic has since been rewritten since the introduction of
|
|
|
|
|
this tunable such that its meaning is deprecated. The value was
|
|
|
|
|
implemented as a bitshift on a score generated by the badness()
|
|
|
|
|
function that did not have any precise units of measure. With the
|
|
|
|
|
rewrite, the score is given as a proportion of available memory to the
|
|
|
|
|
task allocating pages, so using a bitshift which grows the score
|
|
|
|
|
exponentially is, thus, impossible to tune with fine granularity.
|
|
|
|
|
|
|
|
|
|
A much more powerful interface, /proc/<pid>/oom_score_adj, was
|
|
|
|
|
introduced with the oom killer rewrite that allows users to increase or
|
2011-07-26 00:12:17 +00:00
|
|
|
decrease the badness score linearly. This interface will replace
|
2010-08-10 00:19:47 +00:00
|
|
|
/proc/<pid>/oom_adj.
|
|
|
|
|
|
|
|
|
|
A warning will be emitted to the kernel log if an application uses this
|
|
|
|
|
deprecated interface. After it is printed once, future warnings will be
|
|
|
|
|
suppressed until the kernel is rebooted.
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2011-01-13 01:00:12 +00:00
|
|
|
|
2006-03-24 11:18:22 +00:00
|
|
|
What: remove EXPORT_SYMBOL(kernel_thread)
|
|
|
|
|
When: August 2006
|
|
|
|
|
Files: arch/*/kernel/*_ksyms.c
|
2007-07-19 08:48:34 +00:00
|
|
|
Check: kernel_thread
|
2006-03-24 11:18:22 +00: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 11:26:45 +00: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 04:17:09 +00:00
|
|
|
What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
|
2006-10-01 02:41:43 +00:00
|
|
|
When: October 2008
|
2006-08-13 04:17:09 +00: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-13 21:45:52 +00:00
|
|
|
|
2007-01-29 03:02:30 +00:00
|
|
|
What: ACPI procfs interface
|
2007-07-18 09:23:24 +00: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 03:02:30 +00:00
|
|
|
Who: Zhang Rui <rui.zhang@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2011-01-10 03:16:30 +00:00
|
|
|
What: CONFIG_ACPI_PROCFS_POWER
|
|
|
|
|
When: 2.6.39
|
|
|
|
|
Why: sysfs I/F for ACPI power devices, including AC and Battery,
|
2011-05-10 08:16:21 +00:00
|
|
|
has been working in upstream kernel since 2.6.24, Sep 2007.
|
2011-01-10 03:16:30 +00:00
|
|
|
In 2.6.37, we make the sysfs I/F always built in and this option
|
|
|
|
|
disabled by default.
|
|
|
|
|
Remove this option and the ACPI power procfs interface in 2.6.39.
|
|
|
|
|
Who: Zhang Rui <rui.zhang@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-08-23 19:20:26 +00: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-10-11 09:20:05 +00:00
|
|
|
What: i386/x86_64 bzImage symlinks
|
2008-04-10 08:12:27 +00:00
|
|
|
When: April 2010
|
2007-10-11 09:20:05 +00: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 02:40:14 +00:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-04-02 23:57:06 +00: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-28 22:47:41 +00:00
|
|
|
What: b43 support for firmware revision < 410
|
2008-12-27 17:26:39 +00: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-28 22:47:41 +00: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.
|
2011-07-04 18:50:05 +00:00
|
|
|
Who: Michael Buesch <m@bues.ch>
|
2008-02-10 07:08:53 +00:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-31 22:21:26 +00: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-07-10 09:16:47 +00: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-21 17:01:34 +00:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-03-09 19:14:37 +00: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 13:34:05 +00:00
|
|
|
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
2009-03-20 20:56:56 +00: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 15:02:13 +00:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2009-06-02 11:01:38 +00: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 10:02:23 +00:00
|
|
|
|
2009-04-28 21:18:26 +00:00
|
|
|
----------------------------
|
2009-08-06 09:14:26 +00:00
|
|
|
|
|
|
|
|
What: sound-slot/service-* module aliases and related clutters in
|
|
|
|
|
sound/sound_core.c
|
|
|
|
|
When: August 2010
|
|
|
|
|
Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
|
|
|
|
|
(14) and requests modules using custom sound-slot/service-*
|
|
|
|
|
module aliases. The only benefit of doing this is allowing
|
|
|
|
|
use of custom module aliases which might as well be considered
|
|
|
|
|
a bug at this point. This preemptive claiming prevents
|
|
|
|
|
alternative OSS implementations.
|
|
|
|
|
|
|
|
|
|
Till the feature is removed, the kernel will be requesting
|
|
|
|
|
both sound-slot/service-* and the standard char-major-* module
|
|
|
|
|
aliases and allow turning off the pre-claiming selectively via
|
|
|
|
|
CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss
|
|
|
|
|
kernel parameter.
|
|
|
|
|
|
|
|
|
|
After the transition phase is complete, both the custom module
|
|
|
|
|
aliases and switches to disable it will go away. This removal
|
|
|
|
|
will also allow making ALSA OSS emulation independent of
|
|
|
|
|
sound_core. The dependency will be broken then too.
|
|
|
|
|
Who: Tejun Heo <tj@kernel.org>
|
2009-09-29 17:25:24 +00:00
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2010-02-24 11:05:16 +00:00
|
|
|
What: sysfs-class-rfkill state file
|
|
|
|
|
When: Feb 2014
|
|
|
|
|
Files: net/rfkill/core.c
|
|
|
|
|
Why: Documented as obsolete since Feb 2010. This file is limited to 3
|
|
|
|
|
states while the rfkill drivers can have 4 states.
|
|
|
|
|
Who: anybody or Florian Mickler <florian@mickler.org>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: sysfs-class-rfkill claim file
|
|
|
|
|
When: Feb 2012
|
|
|
|
|
Files: net/rfkill/core.c
|
|
|
|
|
Why: It is not possible to claim an rfkill driver since 2007. This is
|
|
|
|
|
Documented as obsolete since Feb 2010.
|
|
|
|
|
Who: anybody or Florian Mickler <florian@mickler.org>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2010-01-26 14:30:06 +00:00
|
|
|
What: KVM paravirt mmu host support
|
|
|
|
|
When: January 2011
|
|
|
|
|
Why: The paravirt mmu host support is slower than non-paravirt mmu, both
|
|
|
|
|
on newer and older hardware. It is already not exposed to the guest,
|
|
|
|
|
and kept only for live migration purposes.
|
|
|
|
|
Who: Avi Kivity <avi@redhat.com>
|
2010-03-05 21:12:34 +00:00
|
|
|
|
|
|
|
|
----------------------------
|
2010-03-14 20:28:46 +00:00
|
|
|
|
2010-03-22 16:17:39 +00:00
|
|
|
What: iwlwifi 50XX module parameters
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.0
|
2010-03-22 16:17:39 +00:00
|
|
|
Why: The "..50" modules parameters were used to configure 5000 series and
|
|
|
|
|
up devices; different set of module parameters also available for 4965
|
|
|
|
|
with same functionalities. Consolidate both set into single place
|
|
|
|
|
in drivers/net/wireless/iwlwifi/iwl-agn.c
|
|
|
|
|
|
|
|
|
|
Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
|
2010-03-23 17:17:03 +00:00
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: iwl4965 alias support
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.0
|
2010-03-23 17:17:03 +00:00
|
|
|
Why: Internal alias support has been present in module-init-tools for some
|
|
|
|
|
time, the MODULE_ALIAS("iwl4965") boilerplate aliases can be removed
|
|
|
|
|
with no impact.
|
|
|
|
|
|
|
|
|
|
Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
|
2010-04-20 14:02:01 +00:00
|
|
|
|
2010-03-16 17:25:12 +00:00
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: xt_NOTRACK
|
|
|
|
|
Files: net/netfilter/xt_NOTRACK.c
|
|
|
|
|
When: April 2011
|
|
|
|
|
Why: Superseded by xt_CT
|
|
|
|
|
Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
|
2010-05-12 07:05:35 +00:00
|
|
|
|
2010-05-20 00:09:40 +00:00
|
|
|
----------------------------
|
|
|
|
|
|
2010-03-26 00:06:55 +00:00
|
|
|
What: IRQF_DISABLED
|
|
|
|
|
When: 2.6.36
|
|
|
|
|
Why: The flag is a NOOP as we run interrupt handlers with interrupts disabled
|
|
|
|
|
Who: Thomas Gleixner <tglx@linutronix.de>
|
2010-05-20 00:09:40 +00:00
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2010-08-11 01:03:26 +00:00
|
|
|
What: PCI DMA unmap state API
|
|
|
|
|
When: August 2012
|
|
|
|
|
Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced
|
|
|
|
|
with DMA unmap state API (DMA unmap state API can be used for
|
|
|
|
|
any bus).
|
|
|
|
|
Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2010-08-11 01:03:26 +00:00
|
|
|
|
2010-10-06 14:42:43 +00:00
|
|
|
What: iwlwifi disable_hw_scan module parameters
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.0
|
2010-10-06 14:42:43 +00:00
|
|
|
Why: Hareware scan is the prefer method for iwlwifi devices for
|
|
|
|
|
scanning operation. Remove software scan support for all the
|
|
|
|
|
iwlwifi devices.
|
|
|
|
|
|
|
|
|
|
Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2010-10-26 16:55:25 +00:00
|
|
|
|
2011-01-12 20:55:10 +00:00
|
|
|
What: Legacy, non-standard chassis intrusion detection interface.
|
|
|
|
|
When: June 2011
|
|
|
|
|
Why: The adm9240, w83792d and w83793 hardware monitoring drivers have
|
|
|
|
|
legacy interfaces for chassis intrusion detection. A standard
|
|
|
|
|
interface has been added to each driver, so the legacy interface
|
|
|
|
|
can be removed.
|
|
|
|
|
Who: Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-02-01 23:52:31 +00:00
|
|
|
|
2011-01-18 16:32:40 +00:00
|
|
|
What: xt_connlimit rev 0
|
|
|
|
|
When: 2012
|
|
|
|
|
Who: Jan Engelhardt <jengelh@medozas.de>
|
|
|
|
|
Files: net/netfilter/xt_connlimit.c
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-02-20 03:17:35 +00:00
|
|
|
|
2011-03-15 19:16:20 +00:00
|
|
|
What: ipt_addrtype match include file
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: superseded by xt_addrtype
|
|
|
|
|
Who: Florian Westphal <fw@strlen.de>
|
|
|
|
|
Files: include/linux/netfilter_ipv4/ipt_addrtype.h
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-03-20 13:50:53 +00:00
|
|
|
|
|
|
|
|
What: i2c_driver.attach_adapter
|
|
|
|
|
i2c_driver.detach_adapter
|
|
|
|
|
When: September 2011
|
|
|
|
|
Why: These legacy callbacks should no longer be used as i2c-core offers
|
|
|
|
|
a variety of preferable alternative ways to instantiate I2C devices.
|
|
|
|
|
Who: Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2010-10-12 15:11:30 +00:00
|
|
|
|
|
|
|
|
What: Support for UVCIOC_CTRL_ADD in the uvcvideo driver
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.2
|
2010-10-12 15:11:30 +00:00
|
|
|
Why: The information passed to the driver by this ioctl is now queried
|
|
|
|
|
dynamically from the device.
|
|
|
|
|
Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Support for UVCIOC_CTRL_MAP_OLD in the uvcvideo driver
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.2
|
2010-10-12 15:11:30 +00:00
|
|
|
Why: Used only by applications compiled against older driver versions.
|
|
|
|
|
Superseded by UVCIOC_CTRL_MAP which supports V4L2 menu controls.
|
|
|
|
|
Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Support for UVCIOC_CTRL_GET and UVCIOC_CTRL_SET in the uvcvideo driver
|
2011-06-09 22:03:03 +00:00
|
|
|
When: 3.2
|
2010-10-12 15:11:30 +00:00
|
|
|
Why: Superseded by the UVCIOC_CTRL_QUERY ioctl.
|
|
|
|
|
Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-06-13 12:38:54 +00:00
|
|
|
|
2011-07-03 18:02:10 +00:00
|
|
|
What: Support for driver specific ioctls in the pwc driver (everything
|
|
|
|
|
defined in media/pwc-ioctl.h)
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: This stems from the v4l1 era, with v4l2 everything can be done with
|
|
|
|
|
standardized v4l2 API calls
|
|
|
|
|
Who: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Driver specific sysfs API in the pwc driver
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: Setting pan/tilt should be done with v4l2 controls, like with other
|
|
|
|
|
cams. The button is available as a standard input device
|
|
|
|
|
Who: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Driver specific use of pixfmt.priv in the pwc driver
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: The .priv field never was intended for this, setting a framerate is
|
|
|
|
|
support using the standardized S_PARM ioctl
|
|
|
|
|
Who: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Software emulation of arbritary resolutions in the pwc driver
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: The pwc driver claims to support any resolution between 160x120
|
|
|
|
|
and 640x480, but emulates this by simply drawing a black border
|
|
|
|
|
around the image. Userspace can draw its own black border if it
|
|
|
|
|
really wants one.
|
|
|
|
|
Who: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
2011-06-13 12:38:54 +00:00
|
|
|
What: For VIDIOC_S_FREQUENCY the type field must match the device node's type.
|
|
|
|
|
If not, return -EINVAL.
|
|
|
|
|
When: 3.2
|
|
|
|
|
Why: It makes no sense to switch the tuner to radio mode by calling
|
|
|
|
|
VIDIOC_S_FREQUENCY on a video node, or to switch the tuner to tv mode by
|
|
|
|
|
calling VIDIOC_S_FREQUENCY on a radio node. This is the first step of a
|
|
|
|
|
move to more consistent handling of tv and radio tuners.
|
|
|
|
|
Who: Hans Verkuil <hans.verkuil@cisco.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
|
What: Opening a radio device node will no longer automatically switch the
|
|
|
|
|
tuner mode from tv to radio.
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: Just opening a V4L device should not change the state of the hardware
|
|
|
|
|
like that. It's very unexpected and against the V4L spec. Instead, you
|
|
|
|
|
switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second
|
|
|
|
|
and last step of the move to consistent handling of tv and radio tuners.
|
|
|
|
|
Who: Hans Verkuil <hans.verkuil@cisco.com>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-07-26 06:08:32 +00:00
|
|
|
|
2011-06-15 20:31:37 +00:00
|
|
|
What: g_file_storage driver
|
|
|
|
|
When: 3.8
|
|
|
|
|
Why: This driver has been superseded by g_mass_storage.
|
|
|
|
|
Who: Alan Stern <stern@rowland.harvard.edu>
|
|
|
|
|
|
|
|
|
|
----------------------------
|
2011-05-31 06:52:22 +00:00
|
|
|
|
|
|
|
|
What: threeg and interface sysfs files in /sys/devices/platform/acer-wmi
|
|
|
|
|
When: 2012
|
|
|
|
|
Why: In 3.0, we can now autodetect internal 3G device and already have
|
|
|
|
|
the threeg rfkill device. So, we plan to remove threeg sysfs support
|
|
|
|
|
for it's no longer necessary.
|
|
|
|
|
|
|
|
|
|
We also plan to remove interface sysfs file that exposed which ACPI-WMI
|
|
|
|
|
interface that was used by acer-wmi driver. It will replaced by
|
|
|
|
|
information log when acer-wmi initial.
|
|
|
|
|
Who: Lee, Chun-Yi <jlee@novell.com>
|
2011-08-24 05:57:51 +00:00
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
|
What: The XFS nodelaylog mount option
|
|
|
|
|
When: 3.3
|
|
|
|
|
Why: The delaylog mode that has been the default since 2.6.39 has proven
|
|
|
|
|
stable, and the old code is in the way of additional improvements in
|
|
|
|
|
the log code.
|
|
|
|
|
Who: Christoph Hellwig <hch@lst.de>
|
