diff --git a/[refs] b/[refs] index aa948f1fcf37..7d7aa1edf500 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 2f67a0695dc389247c05041b05d2a2b06fc102a3 +refs/heads/master: 204470272c3b055b352d5f127d5d5c7dce5fa597 diff --git a/trunk/.gitignore b/trunk/.gitignore index 3016ed30526d..fdcce40226d7 100644 --- a/trunk/.gitignore +++ b/trunk/.gitignore @@ -27,7 +27,6 @@ TAGS vmlinux* !vmlinux.lds.S System.map -Module.markers Module.symvers !.gitignore diff --git a/trunk/Documentation/00-INDEX b/trunk/Documentation/00-INDEX index 1977fab38656..a82a113b4a4b 100644 --- a/trunk/Documentation/00-INDEX +++ b/trunk/Documentation/00-INDEX @@ -329,6 +329,8 @@ sgi-visws.txt - short blurb on the SGI Visual Workstations. sh/ - directory with info on porting Linux to a new architecture. +smart-config.txt + - description of the Smart Config makefile feature. sound/ - directory with info on sound card support. sparc/ diff --git a/trunk/Documentation/ABI/stable/sysfs-class-ubi b/trunk/Documentation/ABI/stable/sysfs-class-ubi deleted file mode 100644 index 18d471d9faea..000000000000 --- a/trunk/Documentation/ABI/stable/sysfs-class-ubi +++ /dev/null @@ -1,212 +0,0 @@ -What: /sys/class/ubi/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - The ubi/ class sub-directory belongs to the UBI subsystem and - provides general UBI information, per-UBI device information - and per-UBI volume information. - -What: /sys/class/ubi/version -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - This file contains version of the latest supported UBI on-media - format. Currently it is 1, and there is no plan to change this. - However, if in the future UBI needs on-flash format changes - which cannot be done in a compatible manner, a new format - version will be added. So this is a mechanism for possible - future backward-compatible (but forward-incompatible) - improvements. - -What: /sys/class/ubiX/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - The /sys/class/ubi0, /sys/class/ubi1, etc directories describe - UBI devices (UBI device 0, 1, etc). They contain general UBI - device information and per UBI volume information (each UBI - device may have many UBI volumes) - -What: /sys/class/ubi/ubiX/avail_eraseblocks -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Amount of available logical eraseblock. For example, one may - create a new UBI volume which has this amount of logical - eraseblocks. - -What: /sys/class/ubi/ubiX/bad_peb_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Count of bad physical eraseblocks on the underlying MTD device. - -What: /sys/class/ubi/ubiX/bgt_enabled -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Contains ASCII "0\n" if the UBI background thread is disabled, - and ASCII "1\n" if it is enabled. - -What: /sys/class/ubi/ubiX/dev -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Major and minor numbers of the character device corresponding - to this UBI device (in : format). - -What: /sys/class/ubi/ubiX/eraseblock_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Maximum logical eraseblock size this UBI device may provide. UBI - volumes may have smaller logical eraseblock size because of their - alignment. - -What: /sys/class/ubi/ubiX/max_ec -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Maximum physical eraseblock erase counter value. - -What: /sys/class/ubi/ubiX/max_vol_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Maximum number of volumes which this UBI device may have. - -What: /sys/class/ubi/ubiX/min_io_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Minimum input/output unit size. All the I/O may only be done - in fractions of the contained number. - -What: /sys/class/ubi/ubiX/mtd_num -Date: January 2008 -KernelVersion: 2.6.25 -Contact: Artem Bityutskiy -Description: - Number of the underlying MTD device. - -What: /sys/class/ubi/ubiX/reserved_for_bad -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Number of physical eraseblocks reserved for bad block handling. - -What: /sys/class/ubi/ubiX/total_eraseblocks -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Total number of good (not marked as bad) physical eraseblocks on - the underlying MTD device. - -What: /sys/class/ubi/ubiX/volumes_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Count of volumes on this UBI device. - -What: /sys/class/ubi/ubiX/ubiX_Y/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - The /sys/class/ubi/ubiX/ubiX_0/, /sys/class/ubi/ubiX/ubiX_1/, - etc directories describe UBI volumes on UBI device X (volumes - 0, 1, etc). - -What: /sys/class/ubi/ubiX/ubiX_Y/alignment -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Volume alignment - the value the logical eraseblock size of - this volume has to be aligned on. For example, 2048 means that - logical eraseblock size is multiple of 2048. In other words, - volume logical eraseblock size is UBI device logical eraseblock - size aligned to the alignment value. - -What: /sys/class/ubi/ubiX/ubiX_Y/corrupted -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n" - if it is corrupted (e.g., due to an interrupted volume update). - -What: /sys/class/ubi/ubiX/ubiX_Y/data_bytes -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - The amount of data this volume contains. This value makes sense - only for static volumes, and for dynamic volume it equivalent - to the total volume size in bytes. - -What: /sys/class/ubi/ubiX/ubiX_Y/dev -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Major and minor numbers of the character device corresponding - to this UBI volume (in : format). - -What: /sys/class/ubi/ubiX/ubiX_Y/name -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Volume name. - -What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Count of physical eraseblock reserved for this volume. - Equivalent to the volume size in logical eraseblocks. - -What: /sys/class/ubi/ubiX/ubiX_Y/type -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Volume type. Contains ASCII "dynamic\n" for dynamic volumes and - "static\n" for static volumes. - -What: /sys/class/ubi/ubiX/ubiX_Y/upd_marker -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Contains ASCII "0\n" if the update marker is not set for this - volume, and "1\n" if it is set. The update marker is set when - volume update starts, and cleaned when it ends. So the presence - of the update marker indicates that the volume is being updated - at the moment of the update was interrupted. The later may be - checked using the "corrupted" sysfs file. - -What: /sys/class/ubi/ubiX/ubiX_Y/usable_eb_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy -Description: - Logical eraseblock size of this volume. Equivalent to logical - eraseblock size of the device aligned on the volume alignment - value. diff --git a/trunk/Documentation/DocBook/Makefile b/trunk/Documentation/DocBook/Makefile index 83966e94cc32..b2b6366bba51 100644 --- a/trunk/Documentation/DocBook/Makefile +++ b/trunk/Documentation/DocBook/Makefile @@ -187,11 +187,8 @@ quiet_cmd_fig2png = FIG2PNG $@ ### # Rule to convert a .c file to inline XML documentation - gen_xml = : - quiet_gen_xml = echo ' GEN $@' -silent_gen_xml = : %.xml: %.c - @$($(quiet)gen_xml) + @echo ' GEN $@' @( \ echo ""; \ expand --tabs=8 < $< | \ diff --git a/trunk/Documentation/DocBook/kernel-api.tmpl b/trunk/Documentation/DocBook/kernel-api.tmpl index b7b1482f6e04..488dd4a4945b 100644 --- a/trunk/Documentation/DocBook/kernel-api.tmpl +++ b/trunk/Documentation/DocBook/kernel-api.tmpl @@ -119,7 +119,7 @@ X!Ilib/string.c !Elib/string.c Bit Operations -!Iinclude/asm-x86/bitops.h +!Iinclude/asm-x86/bitops_32.h @@ -645,58 +645,4 @@ X!Idrivers/video/console/fonts.c !Edrivers/i2c/i2c-core.c - - Clock Framework - - - The clock framework defines programming interfaces to support - software management of the system clock tree. - This framework is widely used with System-On-Chip (SOC) platforms - to support power management and various devices which may need - custom clock rates. - Note that these "clocks" don't relate to timekeeping or real - time clocks (RTCs), each of which have separate frameworks. - These struct clk instances may be used - to manage for example a 96 MHz signal that is used to shift bits - into and out of peripherals or busses, or otherwise trigger - synchronous state machine transitions in system hardware. - - - - Power management is supported by explicit software clock gating: - unused clocks are disabled, so the system doesn't waste power - changing the state of transistors that aren't in active use. - On some systems this may be backed by hardware clock gating, - where clocks are gated without being disabled in software. - Sections of chips that are powered but not clocked may be able - to retain their last state. - This low power state is often called a retention - mode. - This mode still incurs leakage currents, especially with finer - circuit geometries, but for CMOS circuits power is mostly used - by clocked state changes. - - - - Power-aware drivers only enable their clocks when the device - they manage is in active use. Also, system sleep states often - differ according to which clock domains are active: while a - "standby" state may allow wakeup from several active domains, a - "mem" (suspend-to-RAM) state may require a more wholesale shutdown - of clocks derived from higher speed PLLs and oscillators, limiting - the number of possible wakeup event sources. A driver's suspend - method may need to be aware of system-specific clock constraints - on the target sleep state. - - - - Some platforms support programmable clock generators. These - can be used by external chips of various kinds, such as other - CPUs, multimedia codecs, and devices with strict requirements - for interface clocking. - - -!Iinclude/linux/clk.h - - diff --git a/trunk/Documentation/HOWTO b/trunk/Documentation/HOWTO index 0291ade44c17..54835610b3d6 100644 --- a/trunk/Documentation/HOWTO +++ b/trunk/Documentation/HOWTO @@ -249,11 +249,9 @@ process is as follows: release a new -rc kernel every week. - Process continues until the kernel is considered "ready", the process should last around 6 weeks. - - Known regressions in each release are periodically posted to the - linux-kernel mailing list. The goal is to reduce the length of - that list to zero before declaring the kernel to be "ready," but, in - the real world, a small number of regressions often remain at - release time. + - A list of known regressions present in each -rc release is + tracked at the following URI: + http://kernelnewbies.org/known_regressions It is worth mentioning what Andrew Morton wrote on the linux-kernel mailing list about kernel releases: @@ -263,7 +261,7 @@ mailing list about kernel releases: 2.6.x.y -stable kernel tree --------------------------- -Kernels with 4-part versions are -stable kernels. They contain +Kernels with 4 digit versions are -stable kernels. They contain relatively small and critical fixes for security problems or significant regressions discovered in a given 2.6.x kernel. @@ -275,10 +273,7 @@ If no 2.6.x.y kernel is available, then the highest numbered 2.6.x kernel is the current stable kernel. 2.6.x.y are maintained by the "stable" team , and are -released as needs dictate. The normal release period is approximately -two weeks, but it can be longer if there are no pressing problems. A -security-related problem, instead, can cause a release to happen almost -instantly. +released almost every other week. The file Documentation/stable_kernel_rules.txt in the kernel tree documents what kinds of changes are acceptable for the -stable tree, and @@ -303,9 +298,7 @@ a while Andrew or the subsystem maintainer pushes it on to Linus for inclusion in mainline. It is heavily encouraged that all new patches get tested in the -mm tree -before they are sent to Linus for inclusion in the main kernel tree. Code -which does not make an appearance in -mm before the opening of the merge -window will prove hard to merge into the mainline. +before they are sent to Linus for inclusion in the main kernel tree. These kernels are not appropriate for use on systems that are supposed to be stable and they are more risky to run than any of the other @@ -361,12 +354,11 @@ Here is a list of some of the different kernel trees available: - SCSI, James Bottomley git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - - x86, Ingo Molnar - git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git - quilt trees: - - USB, Driver Core, and I2C, Greg Kroah-Hartman + - USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ + - x86-64, partly i386, Andi Kleen + ftp.firstfloor.org:/pub/ak/x86_64/quilt/ Other kernel trees can be found listed at http://git.kernel.org/ and in the MAINTAINERS file. @@ -400,8 +392,8 @@ If you want to be advised of the future bug reports, you can subscribe to the bugme-new mailing list (only new bug reports are mailed here) or to the bugme-janitor mailing list (every change in the bugzilla is mailed here) - http://lists.linux-foundation.org/mailman/listinfo/bugme-new - http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors + http://lists.osdl.org/mailman/listinfo/bugme-new + http://lists.osdl.org/mailman/listinfo/bugme-janitors diff --git a/trunk/Documentation/arm/Samsung-S3C24XX/NAND.txt b/trunk/Documentation/arm/Samsung-S3C24XX/NAND.txt deleted file mode 100644 index bc478a3409b8..000000000000 --- a/trunk/Documentation/arm/Samsung-S3C24XX/NAND.txt +++ /dev/null @@ -1,30 +0,0 @@ - S3C24XX NAND Support - ==================== - -Introduction ------------- - -Small Page NAND ---------------- - -The driver uses a 512 byte (1 page) ECC code for this setup. The -ECC code is not directly compatible with the default kernel ECC -code, so the driver enforces its own OOB layout and ECC parameters - -Large Page NAND ---------------- - -The driver is capable of handling NAND flash with a 2KiB page -size, with support for hardware ECC generation and correction. - -Unlike the 512byte page mode, the driver generates ECC data for -each 256 byte block in an 2KiB page. This means that more than -one error in a page can be rectified. It also means that the -OOB layout remains the default kernel layout for these flashes. - - -Document Author ---------------- - -Ben Dooks, Copyright 2007 Simtec Electronics - diff --git a/trunk/Documentation/arm/Samsung-S3C24XX/Overview.txt b/trunk/Documentation/arm/Samsung-S3C24XX/Overview.txt index d04e1e30c47f..c31b76fa66c4 100644 --- a/trunk/Documentation/arm/Samsung-S3C24XX/Overview.txt +++ b/trunk/Documentation/arm/Samsung-S3C24XX/Overview.txt @@ -156,8 +156,6 @@ NAND controller. If there are any problems the latest linux-mtd code can be found from http://www.linux-mtd.infradead.org/ - For more information see Documentation/arm/Samsung-S3C24XX/NAND.txt - Serial ------ diff --git a/trunk/Documentation/device-mapper/dm-crypt.txt b/trunk/Documentation/device-mapper/dm-crypt.txt deleted file mode 100644 index 6680cab2c705..000000000000 --- a/trunk/Documentation/device-mapper/dm-crypt.txt +++ /dev/null @@ -1,52 +0,0 @@ -dm-crypt -========= - -Device-Mapper's "crypt" target provides transparent encryption of block devices -using the kernel crypto API. - -Parameters: - - - Encryption cipher and an optional IV generation mode. - (In format cipher-chainmode-ivopts:ivmode). - Examples: - des - aes-cbc-essiv:sha256 - twofish-ecb - - /proc/crypto contains supported crypto modes - - - Key used for encryption. It is encoded as a hexadecimal number. - You can only use key sizes that are valid for the selected cipher. - - - The IV offset is a sector count that is added to the sector number - before creating the IV. - - - This is the device that is going to be used as backend and contains the - encrypted data. You can specify it as a path like /dev/xxx or a device - number :. - - - Starting sector within the device where the encrypted data begins. - -Example scripts -=============== -LUKS (Linux Unified Key Setup) is now the preferred way to set up disk -encryption with dm-crypt using the 'cryptsetup' utility, see -http://luks.endorphin.org/ - -[[ -#!/bin/sh -# Create a crypt device using dmsetup -dmsetup create crypt1 --table "0 `blockdev --getsize $1` crypt aes-cbc-essiv:sha256 babebabebabebabebabebabebabebabe 0 $1 0" -]] - -[[ -#!/bin/sh -# Create a crypt device using cryptsetup and LUKS header with default cipher -cryptsetup luksFormat $1 -cryptsetup luksOpen $1 crypt1 -]] diff --git a/trunk/Documentation/dontdiff b/trunk/Documentation/dontdiff index 881e6dd03aea..354aec047c0e 100644 --- a/trunk/Documentation/dontdiff +++ b/trunk/Documentation/dontdiff @@ -141,7 +141,6 @@ mkprep mktables mktree modpost -modules.order modversions.h* offset.h offsets.h @@ -172,7 +171,6 @@ sm_tbl* split-include tags tftpboot.img -timeconst.h times.h* tkparse trix_boot.h diff --git a/trunk/Documentation/fb/gxfb.txt b/trunk/Documentation/fb/gxfb.txt deleted file mode 100644 index 2f640903bbb2..000000000000 --- a/trunk/Documentation/fb/gxfb.txt +++ /dev/null @@ -1,52 +0,0 @@ -[This file is cloned from VesaFB/aty128fb] - -What is gxfb? -================= - -This is a graphics framebuffer driver for AMD Geode GX2 based processors. - -Advantages: - - * No need to use AMD's VSA code (or other VESA emulation layer) in the - BIOS. - * It provides a nice large console (128 cols + 48 lines with 1024x768) - without using tiny, unreadable fonts. - * You can run XF68_FBDev on top of /dev/fb0 - * Most important: boot logo :-) - -Disadvantages: - - * graphic mode is slower than text mode... - - -How to use it? -============== - -Switching modes is done using gxfb.mode_option=... boot -parameter or using `fbset' program. - -See Documentation/fb/modedb.txt for more information on modedb -resolutions. - - -X11 -=== - -XF68_FBDev should generally work fine, but it is non-accelerated. - - -Configuration -============= - -You can pass kernel command line options to gxfb with gxfb.