diff options
Diffstat (limited to 'Documentation')
2071 files changed, 0 insertions, 416813 deletions
diff --git a/Documentation/.gitignore b/Documentation/.gitignore deleted file mode 100644 index bcd907b4141..00000000000 --- a/Documentation/.gitignore +++ /dev/null @@ -1,7 +0,0 @@ -filesystems/dnotify_test -laptops/dslm -timers/hpet_example -vm/hugepage-mmap -vm/hugepage-shm -vm/map_hugetlb - diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX deleted file mode 100644 index 49c051380da..00000000000 --- a/Documentation/00-INDEX +++ /dev/null @@ -1,352 +0,0 @@ - -This is a brief list of all the files in ./linux/Documentation and what -they contain. If you add a documentation file, please list it here in -alphabetical order as well, or risk being hunted down like a rabid dog. -Please try and keep the descriptions small enough to fit on one line. - Thanks -- Paul G. - -Following translations are available on the WWW: - - - Japanese, maintained by the JF Project (jf@listserv.linux.or.jp), at - http://linuxjf.sourceforge.jp/ - -00-INDEX - - this file. -ABI/ - - info on kernel <-> userspace ABI and relative interface stability. - -BUG-HUNTING - - brute force method of doing binary search of patches to find bug. -Changes - - list of changes that break older software packages. -CodingStyle - - how the boss likes the C code in the kernel to look. -development-process/ - - An extended tutorial on how to work with the kernel development - process. -DMA-API.txt - - DMA API, pci_ API & extensions for non-consistent memory machines. -DMA-ISA-LPC.txt - - How to do DMA with ISA (and LPC) devices. -DocBook/ - - directory with DocBook templates etc. for kernel documentation. -HOWTO - - the process and procedures of how to do Linux kernel development. -IPMI.txt - - info on Linux Intelligent Platform Management Interface (IPMI) Driver. -IRQ-affinity.txt - - how to select which CPU(s) handle which interrupt events on SMP. -IRQ.txt - - description of what an IRQ is. -ManagementStyle - - how to (attempt to) manage kernel hackers. -RCU/ - - directory with info on RCU (read-copy update). -SAK.txt - - info on Secure Attention Keys. -SM501.txt - - Silicon Motion SM501 multimedia companion chip -SecurityBugs - - procedure for reporting security bugs found in the kernel. -SubmitChecklist - - Linux kernel patch submission checklist. -SubmittingDrivers - - procedure to get a new driver source included into the kernel tree. -SubmittingPatches - - procedure to get a source patch included into the kernel tree. -VGA-softcursor.txt - - how to change your VGA cursor from a blinking underscore. -accounting/ - - documentation on accounting and taskstats. -acpi/ - - info on ACPI-specific hooks in the kernel. -aoe/ - - description of AoE (ATA over Ethernet) along with config examples. -applying-patches.txt - - description of various trees and how to apply their patches. -arm/ - - directory with info about Linux on the ARM architecture. -atomic_ops.txt - - semantics and behavior of atomic and bitmask operations. -auxdisplay/ - - misc. LCD driver documentation (cfag12864b, ks0108). -basic_profiling.txt - - basic instructions for those who wants to profile Linux kernel. -binfmt_misc.txt - - info on the kernel support for extra binary formats. -blackfin/ - - directory with documentation for the Blackfin arch. -block/ - - info on the Block I/O (BIO) layer. -blockdev/ - - info on block devices & drivers -btmrvl.txt - - info on Marvell Bluetooth driver usage. -bus-virt-phys-mapping.txt - - how to access I/O mapped memory from within device drivers. -cachetlb.txt - - describes the cache/TLB flushing interfaces Linux uses. -cdrom/ - - directory with information on the CD-ROM drivers that Linux has. -cgroups/ - - cgroups features, including cpusets and memory controller. -connector/ - - docs on the netlink based userspace<->kernel space communication mod. -console/ - - documentation on Linux console drivers. -cpu-freq/ - - info on CPU frequency and voltage scaling. -cpu-hotplug.txt - - document describing CPU hotplug support in the Linux kernel. -cpu-load.txt - - document describing how CPU load statistics are collected. -cpuidle/ - - info on CPU_IDLE, CPU idle state management subsystem. -cputopology.txt - - documentation on how CPU topology info is exported via sysfs. -crc32.txt - - brief tutorial on CRC computation -cris/ - - directory with info about Linux on CRIS architecture. -crypto/ - - directory with info on the Crypto API. -dcdbas.txt - - information on the Dell Systems Management Base Driver. -debugging-modules.txt - - some notes on debugging modules after Linux 2.6.3. -dell_rbu.txt - - document demonstrating the use of the Dell Remote BIOS Update driver. -device-mapper/ - - directory with info on Device Mapper. -devices.txt - - plain ASCII listing of all the nodes in /dev/ with major minor #'s. -dontdiff - - file containing a list of files that should never be diff'ed. -driver-model/ - - directory with info about Linux driver model. -dvb/ - - info on Linux Digital Video Broadcast (DVB) subsystem. -early-userspace/ - - info about initramfs, klibc, and userspace early during boot. -edac.txt - - information on EDAC - Error Detection And Correction -eisa.txt - - info on EISA bus support. -fault-injection/ - - dir with docs about the fault injection capabilities infrastructure. -fb/ - - directory with info on the frame buffer graphics abstraction layer. -feature-removal-schedule.txt - - list of files and features that are going to be removed. -filesystems/ - - info on the vfs and the various filesystems that Linux supports. -firmware_class/ - - request_firmware() hotplug interface info. -frv/ - - Fujitsu FR-V Linux documentation. -gpio.txt - - overview of GPIO (General Purpose Input/Output) access conventions. -highuid.txt - - notes on the change from 16 bit to 32 bit user/group IDs. -timers/ - - info on the timer related topics -hw_random.txt - - info on Linux support for random number generator in i8xx chipsets. -hwmon/ - - directory with docs on various hardware monitoring drivers. -i2c/ - - directory with info about the I2C bus/protocol (2 wire, kHz speed). -i2o/ - - directory with info about the Linux I2O subsystem. -x86/i386/ - - directory with info about Linux on Intel 32 bit architecture. -ia64/ - - directory with info about Linux on Intel 64 bit architecture. -infiniband/ - - directory with documents concerning Linux InfiniBand support. -initrd.txt - - how to use the RAM disk as an initial/temporary root filesystem. -input/ - - info on Linux input device support. -io-mapping.txt - - description of io_mapping functions in linux/io-mapping.h -io_ordering.txt - - info on ordering I/O writes to memory-mapped addresses. -ioctl/ - - directory with documents describing various IOCTL calls. -iostats.txt - - info on I/O statistics Linux kernel provides. -irqflags-tracing.txt - - how to use the irq-flags tracing feature. -isapnp.txt - - info on Linux ISA Plug & Play support. -isdn/ - - directory with info on the Linux ISDN support, and supported cards. -java.txt - - info on the in-kernel binary support for Java(tm). -kbuild/ - - directory with info about the kernel build process. -kdump/ - - directory with mini HowTo on getting the crash dump code to work. -kernel-doc-nano-HOWTO.txt - - mini HowTo on generation and location of kernel documentation files. -kernel-docs.txt - - listing of various WWW + books that document kernel internals. -kernel-parameters.txt - - summary listing of command line / boot prompt args for the kernel. -kobject.txt - - info of the kobject infrastructure of the Linux kernel. -kprobes.txt - - documents the kernel probes debugging feature. -kref.txt - - docs on adding reference counters (krefs) to kernel objects. -laptops/ - - directory with laptop related info and laptop driver documentation. -ldm.txt - - a brief description of LDM (Windows Dynamic Disks). -leds/ - - directory with info about LED handling under Linux. -local_ops.txt - - semantics and behavior of local atomic operations. -lockdep-design.txt - - documentation on the runtime locking correctness validator. -logo.gif - - full colour GIF image of Linux logo (penguin - Tux). -logo.txt - - info on creator of above logo & site to get additional images from. -m68k/ - - directory with info about Linux on Motorola 68k architecture. -magic-number.txt - - list of magic numbers used to mark/protect kernel data structures. -md.txt - - info on boot arguments for the multiple devices driver. -memory-barriers.txt - - info on Linux kernel memory barriers. -memory-hotplug.txt - - Hotpluggable memory support, how to use and current status. -memory.txt - - info on typical Linux memory problems. -mips/ - - directory with info about Linux on MIPS architecture. -mmc/ - - directory with info about the MMC subsystem -mono.txt - - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. -mutex-design.txt - - info on the generic mutex subsystem. -namespaces/ - - directory with various information about namespaces -netlabel/ - - directory with information on the NetLabel subsystem. -networking/ - - directory with info on various aspects of networking with Linux. -nmi_watchdog.txt - - info on NMI watchdog for SMP systems. -nommu-mmap.txt - - documentation about no-mmu memory mapping support. -numastat.txt - - info on how to read Numa policy hit/miss statistics in sysfs. -oops-tracing.txt - - how to decode those nasty internal kernel error dump messages. -padata.txt - - An introduction to the "padata" parallel execution API -parisc/ - - directory with info on using Linux on PA-RISC architecture. -parport.txt - - how to use the parallel-port driver. -parport-lowlevel.txt - - description and usage of the low level parallel port functions. -pcmcia/ - - info on the Linux PCMCIA driver. -pi-futex.txt - - documentation on lightweight PI-futexes. -pnp.txt - - Linux Plug and Play documentation. -power/ - - directory with info on Linux PCI power management. -powerpc/ - - directory with info on using Linux with the PowerPC. -preempt-locking.txt - - info on locking under a preemptive kernel. -printk-formats.txt - - how to get printk format specifiers right -prio_tree.txt - - info on radix-priority-search-tree use for indexing vmas. -ramoops.txt - - documentation of the ramoops oops/panic logging module. -rbtree.txt - - info on what red-black trees are and what they are for. -robust-futex-ABI.txt - - documentation of the robust futex ABI. -robust-futexes.txt - - a description of what robust futexes are. -rt-mutex-design.txt - - description of the RealTime mutex implementation design. -rt-mutex.txt - - desc. of RT-mutex subsystem with PI (Priority Inheritance) support. -rtc.txt - - notes on how to use the Real Time Clock (aka CMOS clock) driver. -s390/ - - directory with info on using Linux on the IBM S390. -scheduler/ - - directory with info on the scheduler. -scsi/ - - directory with info on Linux scsi support. -security/ - - directory that contains security-related info -serial/ - - directory with info on the low level serial API. -serial-console.txt - - how to set up Linux with a serial line console as the default. -sgi-ioc4.txt - - description of the SGI IOC4 PCI (multi function) device. -sgi-visws.txt - - short blurb on the SGI Visual Workstations. -sh/ - - directory with info on porting Linux to a new architecture. -sound/ - - directory with info on sound card support. -sparc/ - - directory with info on using Linux on Sparc architecture. -sparse.txt - - info on how to obtain and use the sparse tool for typechecking. -spi/ - - overview of Linux kernel Serial Peripheral Interface (SPI) support. -spinlocks.txt - - info on using spinlocks to provide exclusive access in kernel. -stable_api_nonsense.txt - - info on why the kernel does not have a stable in-kernel api or abi. -stable_kernel_rules.txt - - rules and procedures for the -stable kernel releases. -svga.txt - - short guide on selecting video modes at boot via VGA BIOS. -sysfs-rules.txt - - How not to use sysfs. -sysctl/ - - directory with info on the /proc/sys/* files. -sysrq.txt - - info on the magic SysRq key. -telephony/ - - directory with info on telephony (e.g. voice over IP) support. -unicode.txt - - info on the Unicode character/font mapping used in Linux. -unshare.txt - - description of the Linux unshare system call. -usb/ - - directory with info regarding the Universal Serial Bus. -video-output.txt - - sysfs class driver interface to enable/disable a video output device. -video4linux/ - - directory with info regarding video/TV/radio cards and linux. -vm/ - - directory with info on the Linux vm code. -volatile-considered-harmful.txt - - Why the "volatile" type class should not be used -w1/ - - directory with documents regarding the 1-wire (w1) subsystem. -watchdog/ - - how to auto-reboot Linux if it has "fallen and can't get up". ;-) -x86/x86_64/ - - directory with info on Linux support for AMD x86-64 (Hammer) machines. -zorro.txt - - info on writing drivers for Zorro bus devices found on Amigas. diff --git a/Documentation/ABI/README b/Documentation/ABI/README deleted file mode 100644 index 9feaf16f161..00000000000 --- a/Documentation/ABI/README +++ /dev/null @@ -1,77 +0,0 @@ -This directory attempts to document the ABI between the Linux kernel and -userspace, and the relative stability of these interfaces. Due to the -everchanging nature of Linux, and the differing maturity levels, these -interfaces should be used by userspace programs in different ways. - -We have four different levels of ABI stability, as shown by the four -different subdirectories in this location. Interfaces may change levels -of stability according to the rules described below. - -The different levels of stability are: - - stable/ - This directory documents the interfaces that the developer has - defined to be stable. Userspace programs are free to use these - interfaces with no restrictions, and backward compatibility for - them will be guaranteed for at least 2 years. Most interfaces - (like syscalls) are expected to never change and always be - available. - - testing/ - This directory documents interfaces that are felt to be stable, - as the main development of this interface has been completed. - The interface can be changed to add new features, but the - current interface will not break by doing this, unless grave - errors or security problems are found in them. Userspace - programs can start to rely on these interfaces, but they must be - aware of changes that can occur before these interfaces move to - be marked stable. Programs that use these interfaces are - strongly encouraged to add their name to the description of - these interfaces, so that the kernel developers can easily - notify them if any changes occur (see the description of the - layout of the files below for details on how to do this.) - - obsolete/ - This directory documents interfaces that are still remaining in - the kernel, but are marked to be removed at some later point in - time. The description of the interface will document the reason - why it is obsolete and when it can be expected to be removed. - The file Documentation/feature-removal-schedule.txt may describe - some of these interfaces, giving a schedule for when they will - be removed. - - removed/ - This directory contains a list of the old interfaces that have - been removed from the kernel. - -Every file in these directories will contain the following information: - -What: Short description of the interface -Date: Date created -KernelVersion: Kernel version this feature first showed up in. -Contact: Primary contact for this interface (may be a mailing list) -Description: Long description of the interface and how to use it. -Users: All users of this interface who wish to be notified when - it changes. This is very important for interfaces in - the "testing" stage, so that kernel developers can work - with userspace developers to ensure that things do not - break in ways that are unacceptable. It is also - important to get feedback for these interfaces to make - sure they are working in a proper way and do not need to - be changed further. - - -How things move between levels: - -Interfaces in stable may move to obsolete, as long as the proper -notification is given. - -Interfaces may be removed from obsolete and the kernel as long as the -documented amount of time has gone by. - -Interfaces in the testing state can move to the stable state when the -developers feel they are finished. They cannot be removed from the -kernel tree without going through the obsolete state first. - -It's up to the developer to place their interfaces in the category they -wish for it to start out in. diff --git a/Documentation/ABI/obsolete/proc-pid-oom_adj b/Documentation/ABI/obsolete/proc-pid-oom_adj deleted file mode 100644 index 9a3cb88ade4..00000000000 --- a/Documentation/ABI/obsolete/proc-pid-oom_adj +++ /dev/null @@ -1,22 +0,0 @@ -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 - decrease the badness score linearly. This interface will replace - /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. diff --git a/Documentation/ABI/obsolete/sysfs-bus-usb b/Documentation/ABI/obsolete/sysfs-bus-usb deleted file mode 100644 index bd096d33fbc..00000000000 --- a/Documentation/ABI/obsolete/sysfs-bus-usb +++ /dev/null @@ -1,31 +0,0 @@ -What: /sys/bus/usb/devices/.../power/level -Date: March 2007 -KernelVersion: 2.6.21 -Contact: Alan Stern <stern@rowland.harvard.edu> -Description: - Each USB device directory will contain a file named - power/level. This file holds a power-level setting for - the device, either "on" or "auto". - - "on" means that the device is not allowed to autosuspend, - although normal suspends for system sleep will still - be honored. "auto" means the device will autosuspend - and autoresume in the usual manner, according to the - capabilities of its driver. - - During normal use, devices should be left in the "auto" - level. The "on" level is meant for administrative uses. - If you want to suspend a device immediately but leave it - free to wake up in response to I/O requests, you should - write "0" to power/autosuspend. - - Device not capable of proper suspend and resume should be - left in the "on" level. Although the USB spec requires - devices to support suspend/resume, many of them do not. - In fact so many don't that by default, the USB core - initializes all non-hub devices in the "on" level. Some - drivers may change this setting when they are bound. - - This file is deprecated and will be removed after 2010. - Use the power/control file instead; it does exactly the - same thing. diff --git a/Documentation/ABI/obsolete/sysfs-class-rfkill b/Documentation/ABI/obsolete/sysfs-class-rfkill deleted file mode 100644 index ff60ad9eca4..00000000000 --- a/Documentation/ABI/obsolete/sysfs-class-rfkill +++ /dev/null @@ -1,29 +0,0 @@ -rfkill - radio frequency (RF) connector kill switch support - -For details to this subsystem look at Documentation/rfkill.txt. - -What: /sys/class/rfkill/rfkill[0-9]+/state -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: Current state of the transmitter. - This file is deprecated and scheduled to be removed in 2014, - because its not possible to express the 'soft and hard block' - state of the rfkill driver. -Values: A numeric value. - 0: RFKILL_STATE_SOFT_BLOCKED - transmitter is turned off by software - 1: RFKILL_STATE_UNBLOCKED - transmitter is (potentially) active - 2: RFKILL_STATE_HARD_BLOCKED - transmitter is forced off by something outside of - the driver's control. - -What: /sys/class/rfkill/rfkill[0-9]+/claim -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: This file is deprecated because there no longer is a way to - claim just control over a single rfkill instance. - This file is scheduled to be removed in 2012. -Values: 0: Kernel handles events diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus deleted file mode 100644 index c2a270b45b0..00000000000 --- a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/startup_profile -Date: October 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 0-4. - When read, this attribute returns the number of the actual - profile. This value is persistent, so its equivalent to the - profile that's active when the mouse is powered on next time. - When written, this file sets the number of the startup profile - and the mouse activates this profile immediately. - Please use actual_profile, it does the same thing. diff --git a/Documentation/ABI/removed/devfs b/Documentation/ABI/removed/devfs deleted file mode 100644 index 0020c49933c..00000000000 --- a/Documentation/ABI/removed/devfs +++ /dev/null @@ -1,12 +0,0 @@ -What: devfs -Date: July 2005 (scheduled), finally removed in kernel v2.6.18 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - devfs has been unmaintained for a number of years, has unfixable - races, contains a naming policy within the kernel that is - against the LSB, and can be replaced by using udev. - The files fs/devfs/*, include/linux/devfs_fs*.h were removed, - along with the assorted devfs function calls throughout the - kernel tree. - -Users: diff --git a/Documentation/ABI/removed/dv1394 b/Documentation/ABI/removed/dv1394 deleted file mode 100644 index c2310b6676f..00000000000 --- a/Documentation/ABI/removed/dv1394 +++ /dev/null @@ -1,14 +0,0 @@ -What: dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/dv1394/* were character device files, one for each FireWire - controller and for NTSC and PAL respectively, from which DV data - could be received by read() or transmitted by write(). A few - ioctl()s allowed limited control. - This special-purpose interface has been superseded by libraw1394 + - libiec61883 which are functionally equivalent, support HDV, and - transparently work on top of the newer firewire kernel drivers. - -Users: - ffmpeg/libavformat (if configured for DV1394) diff --git a/Documentation/ABI/removed/ip_queue b/Documentation/ABI/removed/ip_queue deleted file mode 100644 index 3243613bc2d..00000000000 --- a/Documentation/ABI/removed/ip_queue +++ /dev/null @@ -1,9 +0,0 @@ -What: ip_queue -Date: finally removed in kernel v3.5.0 -Contact: Pablo Neira Ayuso <pablo@netfilter.org> -Description: - ip_queue has been replaced by nfnetlink_queue which provides - more advanced queueing mechanism to user-space. The ip_queue - module was already announced to become obsolete years ago. - -Users: diff --git a/Documentation/ABI/removed/o2cb b/Documentation/ABI/removed/o2cb deleted file mode 100644 index 20c91adca6d..00000000000 --- a/Documentation/ABI/removed/o2cb +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/o2cb symlink -Date: May 2011 -KernelVersion: 3.0 -Contact: ocfs2-devel@oss.oracle.com -Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is - removed when new versions of ocfs2-tools which know to look - in /sys/fs/o2cb are sufficiently prevalent. Don't code new - software to look here, it should try /sys/fs/o2cb instead. -Users: ocfs2-tools. It's sufficient to mail proposed changes to - ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/removed/raw1394 b/Documentation/ABI/removed/raw1394 deleted file mode 100644 index ec333e67632..00000000000 --- a/Documentation/ABI/removed/raw1394 +++ /dev/null @@ -1,15 +0,0 @@ -What: raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/raw1394 was a character device file that allowed low-level - access to FireWire buses. Its major drawbacks were its inability - to implement sensible device security policies, and its low level - of abstraction that required userspace clients to duplicate much - of the kernel's ieee1394 core functionality. - Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of - firewire-core. - -Users: - libraw1394 (works with firewire-cdev too, transparent to library ABI - users) diff --git a/Documentation/ABI/removed/video1394 b/Documentation/ABI/removed/video1394 deleted file mode 100644 index c39c25aee77..00000000000 --- a/Documentation/ABI/removed/video1394 +++ /dev/null @@ -1,16 +0,0 @@ -What: video1394 (a.k.a. "OHCI-1394 Video support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/video1394/* were character device files, one for each FireWire - controller, which were used for isochronous I/O. It was added as an - alternative to raw1394's isochronous I/O functionality which had - performance issues in its first generation. Any video1394 user had - to use raw1394 + libraw1394 too because video1394 did not provide - asynchronous I/O for device discovery and configuration. - Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of - firewire-core. - -Users: - libdc1394 (works with firewire-cdev too, transparent to library ABI - users) diff --git a/Documentation/ABI/stable/firewire-cdev b/Documentation/ABI/stable/firewire-cdev deleted file mode 100644 index 16d03082736..00000000000 --- a/Documentation/ABI/stable/firewire-cdev +++ /dev/null @@ -1,103 +0,0 @@ -What: /dev/fw[0-9]+ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - The character device files /dev/fw* are the interface between - firewire-core and IEEE 1394 device drivers implemented in - userspace. The ioctl(2)- and read(2)-based ABI is defined and - documented in <linux/firewire-cdev.h>. - - This ABI offers most of the features which firewire-core also - exposes to kernelspace IEEE 1394 drivers. - - Each /dev/fw* is associated with one IEEE 1394 node, which can - be remote or local nodes. Operations on a /dev/fw* file have - different scope: - - The 1394 node which is associated with the file: - - Asynchronous request transmission - - Get the Configuration ROM - - Query node ID - - Query maximum speed of the path between this node - and local node - - The 1394 bus (i.e. "card") to which the node is attached to: - - Isochronous stream transmission and reception - - Asynchronous stream transmission and reception - - Asynchronous broadcast request transmission - - PHY packet transmission and reception - - Allocate, reallocate, deallocate isochronous - resources (channels, bandwidth) at the bus's IRM - - Query node IDs of local node, root node, IRM, bus - manager - - Query cycle time - - Bus reset initiation, bus reset event reception - - All 1394 buses: - - Allocation of IEEE 1212 address ranges on the local - link layers, reception of inbound requests to such - an address range, asynchronous response transmission - to inbound requests - - Addition of descriptors or directories to the local - nodes' Configuration ROM - - Due to the different scope of operations and in order to let - userland implement different access permission models, some - operations are restricted to /dev/fw* files that are associated - with a local node: - - Addition of descriptors or directories to the local - nodes' Configuration ROM - - PHY packet transmission and reception - - A /dev/fw* file remains associated with one particular node - during its entire life time. Bus topology changes, and hence - node ID changes, are tracked by firewire-core. ABI users do not - need to be aware of topology. - - The following file operations are supported: - - open(2) - Currently the only useful flags are O_RDWR. - - ioctl(2) - Initiate various actions. Some take immediate effect, others - are performed asynchronously while or after the ioctl returns. - See the inline documentation in <linux/firewire-cdev.h> for - descriptions of all ioctls. - - poll(2), select(2), epoll_wait(2) etc. - Watch for events to become available to be read. - - read(2) - Receive various events. There are solicited events like - outbound asynchronous transaction completion or isochronous - buffer completion, and unsolicited events such as bus resets, - request reception, or PHY packet reception. Always use a read - buffer which is large enough to receive the largest event that - could ever arrive. See <linux/firewire-cdev.h> for descriptions - of all event types and for which ioctls affect reception of - events. - - mmap(2) - Allocate a DMA buffer for isochronous reception or transmission - and map it into the process address space. The arguments should - be used as follows: addr = NULL, length = the desired buffer - size, i.e. number of packets times size of largest packet, - prot = at least PROT_READ for reception and at least PROT_WRITE - for transmission, flags = MAP_SHARED, fd = the handle to the - /dev/fw*, offset = 0. - - Isochronous reception works in packet-per-buffer fashion except - for multichannel reception which works in buffer-fill mode. - - munmap(2) - Unmap the isochronous I/O buffer from the process address space. - - close(2) - Besides stopping and freeing I/O contexts that were associated - with the file descriptor, back out any changes to the local - nodes' Configuration ROM. Deallocate isochronous channels and - bandwidth at the IRM that were marked for kernel-assisted - re- and deallocation. - -Users: libraw1394 - libdc1394 - tools like jujuutils, fwhack, ... diff --git a/Documentation/ABI/stable/o2cb b/Documentation/ABI/stable/o2cb deleted file mode 100644 index 5eb1545e0b8..00000000000 --- a/Documentation/ABI/stable/o2cb +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/fs/o2cb/ (was /sys/o2cb) -Date: Dec 2005 -KernelVersion: 2.6.16 -Contact: ocfs2-devel@oss.oracle.com -Description: Ocfs2-tools looks at 'interface-revision' for versioning - information. Each logmask/ file controls a set of debug prints - and can be written into with the strings "allow", "deny", or - "off". Reading the file returns the current state. -Users: ocfs2-tools. It's sufficient to mail proposed changes to - ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/stable/syscalls b/Documentation/ABI/stable/syscalls deleted file mode 100644 index c3ae3e7d6a0..00000000000 --- a/Documentation/ABI/stable/syscalls +++ /dev/null @@ -1,10 +0,0 @@ -What: The kernel syscall interface -Description: - This interface matches much of the POSIX interface and is based - on it and other Unix based interfaces. It will only be added to - over time, and not have things removed from it. - - Note that this interface is different for every architecture - that Linux supports. Please see the architecture-specific - documentation for details on the syscall numbers that are to be - mapped to each syscall. diff --git a/Documentation/ABI/stable/sysfs-acpi-pmprofile b/Documentation/ABI/stable/sysfs-acpi-pmprofile deleted file mode 100644 index 964c7a8afb2..00000000000 --- a/Documentation/ABI/stable/sysfs-acpi-pmprofile +++ /dev/null @@ -1,22 +0,0 @@ -What: /sys/firmware/acpi/pm_profile -Date: 03-Nov-2011 -KernelVersion: v3.2 -Contact: linux-acpi@vger.kernel.org -Description: The ACPI pm_profile sysfs interface exports the platform - power management (and performance) requirement expectations - as provided by BIOS. The integer value is directly passed as - retrieved from the FADT ACPI table. -Values: For possible values see ACPI specification: - 5.2.9 Fixed ACPI Description Table (FADT) - Field: Preferred_PM_Profile - - Currently these values are defined by spec: - 0 Unspecified - 1 Desktop - 2 Mobile - 3 Workstation - 4 Enterprise Server - 5 SOHO Server - 6 Appliance PC - 7 Performance Server - >7 Reserved diff --git a/Documentation/ABI/stable/sysfs-bus-firewire b/Documentation/ABI/stable/sysfs-bus-firewire deleted file mode 100644 index 3d484e5dc84..00000000000 --- a/Documentation/ABI/stable/sysfs-bus-firewire +++ /dev/null @@ -1,122 +0,0 @@ -What: /sys/bus/firewire/devices/fw[0-9]+/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 node device attributes. - Read-only. Mutable during the node device's lifetime. - See IEEE 1212 for semantic definitions. - - config_rom - Contents of the Configuration ROM register. - Binary attribute; an array of host-endian u32. - - guid - The node's EUI-64 in the bus information block of - Configuration ROM. - Hexadecimal string representation of an u64. - - -What: /sys/bus/firewire/devices/fw[0-9]+/units -Date: June 2009 -KernelVersion: 2.6.31 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 node device attribute. - Read-only. Mutable during the node device's lifetime. - See IEEE 1212 for semantic definitions. - - units - Summary of all units present in an IEEE 1394 node. - Contains space-separated tuples of specifier_id and - version of each unit present in the node. Specifier_id - and version are hexadecimal string representations of - u24 of the respective unit directory entries. - Specifier_id and version within each tuple are separated - by a colon. - -Users: udev rules to set ownership and access permissions or ACLs of - /dev/fw[0-9]+ character device files - - -What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 unit device attributes. - Read-only. Immutable during the unit device's lifetime. - See IEEE 1212 for semantic definitions. - - modalias - Same as MODALIAS in the uevent at device creation. - - rom_index - Offset of the unit directory within the parent device's - (node device's) Configuration ROM, in quadlets. - Decimal string representation. - - -What: /sys/bus/firewire/devices/*/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - Attributes common to IEEE 1394 node devices and unit devices. - Read-only. Mutable during the node device's lifetime. - Immutable during the unit device's lifetime. - See IEEE 1212 for semantic definitions. - - These attributes are only created if the root directory of an - IEEE 1394 node or the unit directory of an IEEE 1394 unit - actually contains according entries. - - hardware_version - Hexadecimal string representation of an u24. - - hardware_version_name - Contents of a respective textual descriptor leaf. - - model - Hexadecimal string representation of an u24. - - model_name - Contents of a respective textual descriptor leaf. - - specifier_id - Hexadecimal string representation of an u24. - Mandatory in unit directories according to IEEE 1212. - - vendor - Hexadecimal string representation of an u24. - Mandatory in the root directory according to IEEE 1212. - - vendor_name - Contents of a respective textual descriptor leaf. - - version - Hexadecimal string representation of an u24. - Mandatory in unit directories according to IEEE 1212. - - -What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id - formerly - /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id -Date: Feb 2004 -KernelVersion: 2.6.4 -Contact: linux1394-devel@lists.sourceforge.net -Description: - SCSI target port identifier and logical unit identifier of a - logical unit of an SBP-2 target. The identifiers are specified - in SAM-2...SAM-4 annex A. They are persistent and world-wide - unique properties the SBP-2 attached target. - - Read-only attribute, immutable during the target's lifetime. - Format, as exposed by firewire-sbp2 since 2.6.22, May 2007: - Colon-separated hexadecimal string representations of - u64 EUI-64 : u24 directory_ID : u16 LUN - without 0x prefixes, without whitespace. |