Loading .gitignore +1 −0 Original line number Diff line number Diff line Loading @@ -27,6 +27,7 @@ TAGS vmlinux* !vmlinux.lds.S System.map Module.markers Module.symvers !.gitignore Loading Documentation/ABI/stable/sysfs-class-ubi 0 → 100644 +212 −0 Original line number Diff line number Diff line What: /sys/class/ubi/ Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Major and minor numbers of the character device corresponding to this UBI device (in <major>:<minor> format). What: /sys/class/ubi/ubiX/eraseblock_size Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Major and minor numbers of the character device corresponding to this UBI volume (in <major>:<minor> format). What: /sys/class/ubi/ubiX/ubiX_Y/name Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> Description: Volume name. What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Logical eraseblock size of this volume. Equivalent to logical eraseblock size of the device aligned on the volume alignment value. Documentation/DocBook/Makefile +4 −1 Original line number Diff line number Diff line Loading @@ -187,8 +187,11 @@ 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 @echo ' GEN $@' @$($(quiet)gen_xml) @( \ echo "<programlisting>"; \ expand --tabs=8 < $< | \ Loading Documentation/HOWTO +19 −11 Original line number Diff line number Diff line Loading @@ -249,9 +249,11 @@ 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. - A list of known regressions present in each -rc release is tracked at the following URI: http://kernelnewbies.org/known_regressions - 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. It is worth mentioning what Andrew Morton wrote on the linux-kernel mailing list about kernel releases: Loading @@ -261,7 +263,7 @@ mailing list about kernel releases: 2.6.x.y -stable kernel tree --------------------------- Kernels with 4 digit versions are -stable kernels. They contain Kernels with 4-part 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. Loading @@ -273,7 +275,10 @@ 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 <stable@kernel.org>, and are released almost every other week. 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. The file Documentation/stable_kernel_rules.txt in the kernel tree documents what kinds of changes are acceptable for the -stable tree, and Loading @@ -298,7 +303,9 @@ 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. 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. 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 Loading Loading @@ -354,11 +361,12 @@ Here is a list of some of the different kernel trees available: - SCSI, James Bottomley <James.Bottomley@SteelEye.com> git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - x86, Ingo Molnar <mingo@elte.hu> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git quilt trees: - USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de> - USB, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de> kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ - x86-64, partly i386, Andi Kleen <ak@suse.de> 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. Loading Loading @@ -392,8 +400,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.osdl.org/mailman/listinfo/bugme-new http://lists.osdl.org/mailman/listinfo/bugme-janitors http://lists.linux-foundation.org/mailman/listinfo/bugme-new http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors Loading Documentation/arm/Samsung-S3C24XX/NAND.txt 0 → 100644 +30 −0 Original line number Diff line number Diff line 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 Loading
.gitignore +1 −0 Original line number Diff line number Diff line Loading @@ -27,6 +27,7 @@ TAGS vmlinux* !vmlinux.lds.S System.map Module.markers Module.symvers !.gitignore Loading
Documentation/ABI/stable/sysfs-class-ubi 0 → 100644 +212 −0 Original line number Diff line number Diff line What: /sys/class/ubi/ Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Major and minor numbers of the character device corresponding to this UBI device (in <major>:<minor> format). What: /sys/class/ubi/ubiX/eraseblock_size Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Major and minor numbers of the character device corresponding to this UBI volume (in <major>:<minor> format). What: /sys/class/ubi/ubiX/ubiX_Y/name Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> Description: Volume name. What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs Date: July 2006 KernelVersion: 2.6.22 Contact: Artem Bityutskiy <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> 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 <dedekind@infradead.org> Description: Logical eraseblock size of this volume. Equivalent to logical eraseblock size of the device aligned on the volume alignment value.
Documentation/DocBook/Makefile +4 −1 Original line number Diff line number Diff line Loading @@ -187,8 +187,11 @@ 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 @echo ' GEN $@' @$($(quiet)gen_xml) @( \ echo "<programlisting>"; \ expand --tabs=8 < $< | \ Loading
Documentation/HOWTO +19 −11 Original line number Diff line number Diff line Loading @@ -249,9 +249,11 @@ 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. - A list of known regressions present in each -rc release is tracked at the following URI: http://kernelnewbies.org/known_regressions - 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. It is worth mentioning what Andrew Morton wrote on the linux-kernel mailing list about kernel releases: Loading @@ -261,7 +263,7 @@ mailing list about kernel releases: 2.6.x.y -stable kernel tree --------------------------- Kernels with 4 digit versions are -stable kernels. They contain Kernels with 4-part 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. Loading @@ -273,7 +275,10 @@ 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 <stable@kernel.org>, and are released almost every other week. 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. The file Documentation/stable_kernel_rules.txt in the kernel tree documents what kinds of changes are acceptable for the -stable tree, and Loading @@ -298,7 +303,9 @@ 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. 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. 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 Loading Loading @@ -354,11 +361,12 @@ Here is a list of some of the different kernel trees available: - SCSI, James Bottomley <James.Bottomley@SteelEye.com> git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git - x86, Ingo Molnar <mingo@elte.hu> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git quilt trees: - USB, PCI, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de> - USB, Driver Core, and I2C, Greg Kroah-Hartman <gregkh@suse.de> kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/ - x86-64, partly i386, Andi Kleen <ak@suse.de> 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. Loading Loading @@ -392,8 +400,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.osdl.org/mailman/listinfo/bugme-new http://lists.osdl.org/mailman/listinfo/bugme-janitors http://lists.linux-foundation.org/mailman/listinfo/bugme-new http://lists.linux-foundation.org/mailman/listinfo/bugme-janitors Loading
Documentation/arm/Samsung-S3C24XX/NAND.txt 0 → 100644 +30 −0 Original line number Diff line number Diff line 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
