2005-04-16 18:20:36 -04: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.
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-05-08 03:36:28 -04:00
|
|
|
What: MXSER
|
|
|
|
|
When: December 2007
|
|
|
|
|
Why: Old mxser driver is obsoleted by the mxser_new. Give it some time yet
|
|
|
|
|
and remove it.
|
|
|
|
|
Who: Jiri Slaby <jirislaby@gmail.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-03-10 06:10:11 -05:00
|
|
|
What: V4L2 VIDIOC_G_MPEGCOMP and VIDIOC_S_MPEGCOMP
|
|
|
|
|
When: October 2007
|
|
|
|
|
Why: Broken attempt to set MPEG compression parameters. These ioctls are
|
|
|
|
|
not able to implement the wide variety of parameters that can be set
|
|
|
|
|
by hardware MPEG encoders. A new MPEG control mechanism was created
|
|
|
|
|
in kernel 2.6.18 that replaces these ioctls. See the V4L2 specification
|
|
|
|
|
(section 1.9: Extended controls) for more information on this topic.
|
|
|
|
|
Who: Hans Verkuil <hverkuil@xs4all.nl> and
|
|
|
|
|
Mauro Carvalho Chehab <mchehab@infradead.org>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-08-30 16:50:27 -04:00
|
|
|
What: /sys/devices/.../power/state
|
|
|
|
|
dev->power.power_state
|
|
|
|
|
dpm_runtime_{suspend,resume)()
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2005-06-25 17:59:37 -04:00
|
|
|
What: RAW driver (CONFIG_RAW_DRIVER)
|
|
|
|
|
When: December 2005
|
|
|
|
|
Why: declared obsolete since kernel 2.6.3
|
|
|
|
|
O_DIRECT can be used instead
|
|
|
|
|
Who: Adrian Bunk <bunk@stusta.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2005-05-17 00:53:59 -04:00
|
|
|
What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN
|
2006-11-19 18:05:05 -05:00
|
|
|
When: June 2007
|
|
|
|
|
Why: Deprecated in favour of the more efficient and robust rawiso interface.
|
|
|
|
|
Affected are applications which use the deprecated part of libraw1394
|
|
|
|
|
(raw1394_iso_write, raw1394_start_iso_write, raw1394_start_iso_rcv,
|
|
|
|
|
raw1394_stop_iso_rcv) or bypass libraw1394.
|
|
|
|
|
Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
|
2005-05-11 21:59:29 -04:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-04-29 18:05:48 -04:00
|
|
|
What: old NCR53C9x driver
|
|
|
|
|
When: October 2007
|
|
|
|
|
Why: Replaced by the much better esp_scsi driver. Actual low-level
|
2007-05-13 16:48:31 -04:00
|
|
|
driver can be ported over almost trivially.
|
2007-04-29 18:05:48 -04:00
|
|
|
Who: David Miller <davem@davemloft.net>
|
|
|
|
|
Christoph Hellwig <hch@lst.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2005-11-09 00:38:53 -05:00
|
|
|
What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
|
2006-09-06 08:29:00 -04:00
|
|
|
When: December 2006
|
2007-06-01 03:46:48 -04:00
|
|
|
Files: include/linux/video_decoder.h
|
2005-11-09 00:38:53 -05:00
|
|
|
Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
|
|
|
|
|
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.
|
|
|
|
|
Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2005-07-07 20:58:58 -04: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-09 22:44:15 -04:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-03-24 06:18:22 -05:00
|
|
|
What: remove EXPORT_SYMBOL(kernel_thread)
|
|
|
|
|
When: August 2006
|
|
|
|
|
Files: arch/*/kernel/*_ksyms.c
|
2007-06-08 16:46:45 -04:00
|
|
|
Funcs: kernel_thread
|
2006-03-24 06:18:22 -05: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-01-14 16:21:33 -05:00
|
|
|
What: CONFIG_FORCED_INLINING
|
|
|
|
|
When: June 2006
|
|
|
|
|
Why: Config option is there to see if gcc is good enough. (in january
|
|
|
|
|
2006). If it is, the behavior should just be the default. If it's not,
|
|
|
|
|
the option should just go away entirely.
|
|
|
|
|
Who: Arjan van de Ven
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-02-07 01:43:31 -05:00
|
|
|
What: eepro100 network driver
|
|
|
|
|
When: January 2007
|
|
|
|
|
Why: replaced by the e100 driver
|
|
|
|
|
Who: Adrian Bunk <bunk@stusta.de>
|
2006-02-07 01:47:12 -05:00
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-09-01 00:27:46 -04:00
|
|
|
What: drivers depending on OSS_OBSOLETE_DRIVER
|
|
|
|
|
When: options in 2.6.20, code in 2.6.22
|
|
|
|
|
Why: OSS drivers with ALSA replacements
|
|
|
|
|
Who: Adrian Bunk <bunk@stusta.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-06-28 07:26:45 -04: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-03-20 16:17:13 -05:00
|
|
|
What: USB driver API moves to EXPORT_SYMBOL_GPL
|
2006-10-03 16:49:15 -04:00
|
|
|
When: February 2008
|
2006-03-20 16:17:13 -05:00
|
|
|
Files: include/linux/usb.h, drivers/usb/core/driver.c
|
|
|
|
|
Why: The USB subsystem has changed a lot over time, and it has been
|
|
|
|
|
possible to create userspace USB drivers using usbfs/libusb/gadgetfs
|
|
|
|
|
that operate as fast as the USB bus allows. Because of this, the USB
|
|
|
|
|
subsystem will not be allowing closed source kernel drivers to
|
|
|
|
|
register with it, after this grace period is over. If anyone needs
|
|
|
|
|
any help in converting their closed source drivers over to use the
|
|
|
|
|
userspace filesystems, please contact the
|
|
|
|
|
linux-usb-devel@lists.sourceforge.net mailing list, and the developers
|
|
|
|
|
there will be glad to help you out.
|
|
|
|
|
Who: Greg Kroah-Hartman <gregkh@suse.de>
|
2006-03-31 05:29:56 -05:00
|
|
|
|
|
|
|
|
---------------------------
|
2006-06-28 07:28:27 -04:00
|
|
|
|
2006-07-01 22:29:03 -04:00
|
|
|
What: Interrupt only SA_* flags
|
2007-05-08 03:28:56 -04:00
|
|
|
When: September 2007
|
2006-07-01 22:29:03 -04:00
|
|
|
Why: The interrupt related SA_* flags are replaced by IRQF_* to move them
|
|
|
|
|
out of the signal namespace.
|
|
|
|
|
|
|
|
|
|
Who: Thomas Gleixner <tglx@linutronix.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2006-07-01 11:13:37 -04:00
|
|
|
|
2006-08-13 00:17:09 -04:00
|
|
|
What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
|
2006-09-30 22:41:43 -04:00
|
|
|
When: October 2008
|
2006-08-13 00:17:09 -04: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 17:45:52 -04:00
|
|
|
|
|
|
|
|
What: i2c-isa
|
|
|
|
|
When: December 2006
|
|
|
|
|
Why: i2c-isa is a non-sense and doesn't fit in the device driver
|
|
|
|
|
model. Drivers relying on it are better implemented as platform
|
|
|
|
|
drivers.
|
|
|
|
|
Who: Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2006-10-03 04:13:54 -04:00
|
|
|
|
2007-05-01 17:26:27 -04:00
|
|
|
What: i2c_adapter.list
|
2007-01-04 07:07:04 -05:00
|
|
|
When: July 2007
|
2007-05-01 17:26:27 -04:00
|
|
|
Why: Superfluous, this list duplicates the one maintained by the driver
|
|
|
|
|
core.
|
2007-01-04 07:07:04 -05:00
|
|
|
Who: Jean Delvare <khali@linux-fr.org>,
|
|
|
|
|
David Brownell <dbrownell@users.sourceforge.net>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-02-10 04:45:50 -05:00
|
|
|
What: drivers depending on OBSOLETE_OSS
|
|
|
|
|
When: options in 2.6.22, code in 2.6.24
|
|
|
|
|
Why: OSS drivers with ALSA replacements
|
|
|
|
|
Who: Adrian Bunk <bunk@stusta.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2006-10-03 15:34:28 -04:00
|
|
|
What: ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver
|
|
|
|
|
When: December 2006
|
|
|
|
|
Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are
|
|
|
|
|
functionally very much similar. They talk to ACPI in same way. Only
|
|
|
|
|
difference between them is the way they do frequency transitions.
|
|
|
|
|
One uses MSRs and the other one uses IO ports. Functionaliy of
|
|
|
|
|
speedstep_centrino with ACPI hooks is now merged into acpi-cpufreq.
|
|
|
|
|
That means one common driver will support all Intel Enhanced Speedstep
|
|
|
|
|
capable CPUs. That means less confusion over name of
|
|
|
|
|
speedstep-centrino driver (with that driver supposed to be used on
|
|
|
|
|
non-centrino platforms). That means less duplication of code and
|
|
|
|
|
less maintenance effort and no possibility of these two drivers
|
|
|
|
|
going out of sync.
|
|
|
|
|
Current users of speedstep_centrino with ACPI hooks are requested to
|
|
|
|
|
switch over to acpi-cpufreq driver. speedstep-centrino will continue
|
|
|
|
|
to work using older non-ACPI static table based scheme even after this
|
|
|
|
|
date.
|
|
|
|
|
|
|
|
|
|
Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2007-01-11 01:49:44 -05:00
|
|
|
|
|
|
|
|
What: /sys/firmware/acpi/namespace
|
|
|
|
|
When: 2.6.21
|
|
|
|
|
Why: The ACPI namespace is effectively the symbol list for
|
|
|
|
|
the BIOS. The device names are completely arbitrary
|
|
|
|
|
and have no place being exposed to user-space.
|
|
|
|
|
|
|
|
|
|
For those interested in the BIOS ACPI namespace,
|
|
|
|
|
the BIOS can be extracted and disassembled with acpidump
|
|
|
|
|
and iasl as documented in the pmtools package here:
|
|
|
|
|
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils
|
|
|
|
|
Who: Len Brown <len.brown@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-01-28 22:02:30 -05:00
|
|
|
What: ACPI procfs interface
|
|
|
|
|
When: July 2007
|
|
|
|
|
Why: After ACPI sysfs conversion, ACPI attributes will be duplicated
|
|
|
|
|
in sysfs and the ACPI procfs interface should be removed.
|
|
|
|
|
Who: Zhang Rui <rui.zhang@intel.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-01-11 01:49:44 -05: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 00:29:01 -05:00
|
|
|
|
2007-02-07 12:18:30 -05:00
|
|
|
What: sk98lin network driver
|
|
|
|
|
When: July 2007
|
|
|
|
|
Why: In kernel tree version of driver is unmaintained. Sk98lin driver
|
|
|
|
|
replaced by the skge driver.
|
|
|
|
|
Who: Stephen Hemminger <shemminger@osdl.org>
|
|
|
|
|
|
2007-02-10 01:29:11 -05:00
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
What: Compaq touchscreen device emulation
|
|
|
|
|
When: Oct 2007
|
|
|
|
|
Files: drivers/input/tsdev.c
|
|
|
|
|
Why: The code says it was obsolete when it was written in 2001.
|
|
|
|
|
tslib is a userspace library which does anything tsdev can do and
|
|
|
|
|
much more besides in userspace where this code belongs. There is no
|
|
|
|
|
longer any need for tsdev and applications should have converted to
|
|
|
|
|
use tslib by now.
|
|
|
|
|
The name "tsdev" is also extremely confusing and lots of people have
|
|
|
|
|
it loaded when they don't need/use it.
|
|
|
|
|
Who: Richard Purdie <rpurdie@rpsys.net>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2007-03-05 03:30:27 -05:00
|
|
|
|
2007-04-27 04:04:23 -04:00
|
|
|
What: Multipath cached routing support in ipv4
|
|
|
|
|
When: in 2.6.23
|
|
|
|
|
Why: Code was merged, then submitter immediately disappeared leaving
|
|
|
|
|
us with no maintainer and lots of bugs. The code should not have
|
|
|
|
|
been merged in the first place, and many aspects of it's
|
|
|
|
|
implementation are blocking more critical core networking
|
|
|
|
|
development. It's marked EXPERIMENTAL and no distribution
|
|
|
|
|
enables it because it cause obscure crashes due to unfixable bugs
|
|
|
|
|
(interfaces don't return errors so memory allocation can't be
|
|
|
|
|
handled, calling contexts of these interfaces make handling
|
|
|
|
|
errors impossible too because they get called after we've
|
|
|
|
|
totally commited to creating a route object, for example).
|
|
|
|
|
This problem has existed for years and no forward progress
|
|
|
|
|
has ever been made, and nobody steps up to try and salvage
|
|
|
|
|
this code, so we're going to finally just get rid of it.
|
|
|
|
|
Who: David S. Miller <davem@davemloft.net>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2007-05-04 12:47:50 -04:00
|
|
|
|
|
|
|
|
What: read_dev_chars(), read_conf_data{,_lpm}() (s390 common I/O layer)
|
|
|
|
|
When: December 2007
|
|
|
|
|
Why: These functions are a leftover from 2.4 times. They have several
|
|
|
|
|
problems:
|
|
|
|
|
- Duplication of checks that are done in the device driver's
|
|
|
|
|
interrupt handler
|
|
|
|
|
- common I/O layer can't do device specific error recovery
|
|
|
|
|
- device driver can't be notified for conditions happening during
|
|
|
|
|
execution of the function
|
|
|
|
|
Device drivers should issue the read device characteristics and read
|
|
|
|
|
configuration data ccws and do the appropriate error handling
|
|
|
|
|
themselves.
|
|
|
|
|
Who: Cornelia Huck <cornelia.huck@de.ibm.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-05-01 17:26:34 -04:00
|
|
|
What: i2c-ixp2000, i2c-ixp4xx and scx200_i2c drivers
|
|
|
|
|
When: September 2007
|
|
|
|
|
Why: Obsolete. The new i2c-gpio driver replaces all hardware-specific
|
|
|
|
|
I2C-over-GPIO drivers.
|
|
|
|
|
Who: Jean Delvare <khali@linux-fr.org>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
2007-05-08 03:27:14 -04:00
|
|
|
|
|
|
|
|
What: drivers depending on OSS_OBSOLETE
|
|
|
|
|
When: options in 2.6.23, code in 2.6.25
|
|
|
|
|
Why: obsolete OSS drivers
|
|
|
|
|
Who: Adrian Bunk <bunk@stusta.de>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2007-05-17 10:43:26 -04: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-04 15:28:48 -04:00
|
|
|
When: Dec 2008
|
2007-05-17 10:43:26 -04: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-04 15:28:48 -04:00
|
|
|
Because issuing spin down command to an already spun down disk
|
2007-05-17 10:43:26 -04: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-04 15:28:48 -04:00
|
|
|
Who: Tejun Heo <htejun@gmail.com>
|
|
|
|
|
|
|
|
|
|
---------------------------
|
|
|
|
|
|
