mtd/patches Configure.help,1.37,1.38

[rmk at infradead.org]

Update of /home/cvs/mtd/patches
In directory phoenix.infradead.org:/tmp/cvs-serv11403

Modified Files:
	Configure.help 
Log Message:
Merge Configure.help with 2.5.42 drivers/mtd/Config.help

Index: Configure.help
===================================================================
RCS file: /home/cvs/mtd/patches/Configure.help,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- Configure.help	13 Sep 2002 13:41:31 -0000	1.37
+++ Configure.help	14 Oct 2002 11:28:24 -0000	1.38
@@ -15,7 +15,7 @@
 Memory Technology Device (MTD) support
 CONFIG_MTD
   Memory Technology Devices are flash, RAM and similar chips, often
-  used for solid state filesystems on embedded devices. This option
+  used for solid state file systems on embedded devices. This option
   will provide the generic support for MTD drivers to register
   themselves with the kernel and for potential users of MTD devices
   to enumerate the devices which are present and obtain a handle on
@@ -50,8 +50,8 @@
   RedBoot is a ROM monitor and bootloader which deals with multiple
   'images' in flash devices by putting a table in the last erase
   block of the device, similar to a partition table, which gives
-  the offsets, lengths and names of all the images stored in the 
-  flash. 
+  the offsets, lengths and names of all the images stored in the
+  flash.
 
   If you need code which can detect and parse this table, and register
   MTD 'partitions' corresponding to each image in the table, enable
@@ -101,14 +101,14 @@
 CONFIG_MTD_AFS_PARTS
   The ARM Firmware Suite allows the user to divide flash devices into
   multiple 'images'. Each such image has a header containing its name
-  and offset/size etc. 
+  and offset/size etc.
 
-  If you need code which can detect and parse these tables, and register
-  MTD 'partitions' corresponding to each image detected, enable
-  this option. 
+  If you need code which can detect and parse these tables, and
+  register MTD 'partitions' corresponding to each image detected,
+  enable this option.
 
   You will still need the parsing functions to be called by the driver
-  for your particular device. It won't happen automatically. The 
+  for your particular device. It won't happen automatically. The
   'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
 
 MTD debugging verbosity
@@ -127,8 +127,8 @@
 CONFIG_MTD_BLOCK
   Although most flash chips have an erase size too large to be useful
   as block devices, it is possible to use MTD devices which are based
-  on RAM chips in this manner. This block device is a user of MTD devices
-  performing that function.
+  on RAM chips in this manner. This block device is a user of MTD
+  devices performing that function.
 
   At the moment, it is also required for the Journalling Flash File
   System(s) to obtain a handle on the MTD device when it's mounted
@@ -137,7 +137,7 @@
 
   Later, it may be extended to perform read/erase/modify/write cycles
   on flash chips to emulate a smaller block size. Needless to say,
-  this is very unsafe, but could be useful for filesystems which are
+  this is very unsafe, but could be useful for file systems which are
   almost never written to.
 
   You do not need this option for use with the DiskOnChip devices. For
@@ -145,9 +145,9 @@
 
 Readonly block device access to MTD devices
 CONFIG_MTD_BLOCK_RO
-  This allows you to mount read-only filesystems (such as cramfs) from
-  an MTD device, without the overhead (and danger) of the caching 
-  driver. 
+  This allows you to mount read-only file systems (such as cramfs)
+  from an MTD device, without the overhead (and danger) of the caching
+  driver.
 
   You do not need this option for use with the DiskOnChip devices. For
   those, enable NFTL support (CONFIG_NFTL) instead.
@@ -156,8 +156,8 @@
 CONFIG_FTL
   This provides support for the original Flash Translation Layer which
   is part of the PCMCIA specification. It uses a kind of pseudo-
-  filesystem on a flash device to emulate a block device with 512-byte
-  sectors, on top of which you put a 'normal' filesystem.
+  file system on a flash device to emulate a block device with
+  512-byte sectors, on top of which you put a 'normal' file system.
 
   You may find that the algorithms used in this code are patented
   unless you live in the Free World where software patents aren't
@@ -170,8 +170,8 @@
 CONFIG_NFTL
   This provides support for the NAND Flash Translation Layer which is
   used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
-  filesystem on a flash device to emulate a block device with 512-byte
-  sectors, on top of which you put a 'normal' filesystem.
+  file system on a flash device to emulate a block device with
+  512-byte sectors, on top of which you put a 'normal' file system.
 
   You may find that the algorithms used in this code are patented
   unless you live in the Free World where software patents aren't
@@ -182,9 +182,10 @@
 
 Write support for NFTL (EXPERIMENTAL)
 CONFIG_NFTL_RW
-  If you're lucky, this will actually work. Don't whinge if it doesn't.
-  Send mail to the MTD mailing list <linux-mtd at lists.infradead.org> if
-  you want to help to make it more reliable.
+  If you're lucky, this will actually work. Don't whinge if it
+  doesn't.  Send mail to the MTD mailing list
+  <linux-mtd at lists.infradead.org> if you want to help to make it more
+  reliable.
 
 Common Flash Interface (CFI) support
 CONFIG_MTD_CFI
@@ -437,7 +438,7 @@
 CONFIG_MTD_REDWOOD
   This mapping file partitions the CFI flash on the IBM Redwood-4/5 
   board into five partitions for two writable
-  (kernel, filesystem) and three read-only (OpenBIOS Vital
+  (kernel, file system) and three read-only (OpenBIOS Vital
   Product Data, OpenBIOS no-volative storage, OpenBIOS) MTD devices.
 
 Flash chip mapping on TQM8xxL PPC board
@@ -618,7 +619,7 @@
   on NAND flash. If you want to use your NAND flash with JFFS2, 
   you should turn this option on. Otherwise you have not the full
   functionallity of JFFS2 support for NAND flash. To use this
-  option turn on JFFS2 in filesystems.
+  option turn on JFFS2 in file systems.
 
 Support for the SPIA board
 CONFIG_MTD_NAND_SPIA
@@ -646,7 +647,7 @@
 
   If you use this device, you probably also want to enable the NFTL
   'NAND Flash Translation Layer' option below, which is used to emulate
-  a block device by using a kind of filesystem on the flash chips.
+  a block device by using a kind of file system on the flash chips.
 
 Alternative Disk-On-Chip Millennium support
 CONFIG_MTD_DOC2001
@@ -659,7 +660,7 @@
 
   If you use this device, you probably also want to enable the NFTL
   'NAND Flash Translation Layer' option below, which is used to emulate
-  a block device by using a kind of filesystem on the flash chips.
+  a block device by using a kind of file system on the flash chips.
 
 Probe for DiskOnChip devices
 CONFIG_MTD_DOCPROBE
@@ -781,18 +782,18 @@
   allocating space from Linux's available memory. Otherwise, leave 
   this set to zero. Most people will want to leave this as zero.
 
-Support for the Journalling Flash Filesystem
+Support for the Journalling Flash File System
 CONFIG_JFFS_FS
   JFFS is the Journalling Flash File System developed by Axis
   Communications in Sweden, aimed at providing a crash/powerdown-safe
-  filesystem for disk-less embedded devices. Further information is
+  file system for disk-less embedded devices. Further information is
   available at (http://developer.axis.com/software/jffs/).
 
 JFFS debugging verbosity
 CONFIG_JFFS_FS_VERBOSE
   Determines the verbosity level of the JFFS debugging messages.
 
-Journalling Flash Filesystem version 2
+Journalling Flash File System version 2
 CONFIG_JFFS2_FS
   JFFS2 is the second generation of the Journalling Flash File System
   for use on diskless embedded devices. It provides improved wear