yaffs: Remove SHORT_NAMES_IN_RAM and WIDE_TNODE_DISABLE configs

[yaffs2.git] / Kconfig

diff --git a/Kconfig b/Kconfig
index 1d3bb715e6e09ad4854dba7a43ca1e07ecb667a1..635414059997d1efcd89eea9e49cc068bcaf6004 100644 (file)
--- a/Kconfig
+++ b/Kconfig
@@ -102,67 +102,60 @@ config YAFFS_DISABLE_TAGS_ECC
 
          If unsure, say N.
 
-config YAFFS_DISABLE_LAZY_LOAD
-       bool "Disable lazy loading"
-       depends on YAFFS_YAFFS2
+config YAFFS_ALWAYS_CHECK_CHUNK_ERASED
+       bool "Force chunk erase check"
+       depends on YAFFS_FS
        default n
        help
-         "Lazy loading" defers loading file details until they are
-         required. This saves mount time, but makes the first look-up
-         a bit longer.
-
-         Lazy loading will only happen if enabled by this option being 'n'
-         and if the appropriate tags are available, else yaffs2 will
-         automatically fall back to immediate loading and do the right
-         thing.
-
-         Lazy laoding will be required by checkpointing.
+          Normally YAFFS only checks chunks before writing until an erased
+         chunk is found. This helps to detect any partially written
+         chunks that might have happened due to power loss.
 
-         Setting this to 'y' will disable lazy loading.
+         Enabling this forces on the test that chunks are erased in flash
+         before writing to them. This takes more time but is potentially
+         a bit more secure.
 
-         If unsure, say N.
+         Suggest setting Y during development and ironing out driver
+         issues etc. Suggest setting to N if you want faster writing.
 
+         If unsure, say Y.
 
-config YAFFS_DISABLE_WIDE_TNODES
-       bool "Turn off wide tnodes"
+config YAFFS_EMPTY_LOST_AND_FOUND
+       bool "Empty lost and found on boot"
        depends on YAFFS_FS
        default n
        help
-         Wide tnodes are only used for NAND arrays >=32MB for 512-byte
-         page devices and >=128MB for 2k page devices. They use slightly
-         more RAM but are faster since they eliminate chunk group
-         searching.
-
-         Setting this to 'y' will force tnode width to 16 bits and save
-         memory but make large arrays slower.
+         If this is enabled then the contents of lost and found is
+         automatically dumped at mount.
 
          If unsure, say N.
 
-config YAFFS_ALWAYS_CHECK_CHUNK_ERASED
-       bool "Force chunk erase check"
+config YAFFS_DISABLE_BLOCK_REFRESHING
+       bool "Disable yaffs2 block refreshing"
        depends on YAFFS_FS
        default n
        help
-          Normally YAFFS only checks chunks before writing until an erased
-         chunk is found. This helps to detect any partially written
-         chunks that might have happened due to power loss.
+        If this is set, then block refreshing is disabled.
+        Block refreshing infrequently refreshes the oldest block in
+        a yaffs2 file system. This mechanism helps to refresh flash to
+        mitigate against data loss. This is particularly useful for MLC.
 
-         Enabling this forces on the test that chunks are erased in flash
-         before writing to them. This takes more time but is potentially
-         a bit more secure.
+         If unsure, say N.
 
-         Suggest setting Y during development and ironing out driver
-         issues etc. Suggest setting to N if you want faster writing.
+config YAFFS_DISABLE_BACKGROUND
+       bool "Disable yaffs2 background processing"
+       depends on YAFFS_FS
+       default n
+       help
+        If this is set, then background processing is disabled.
+        Background processing makes many foreground activities faster.
 
-         If unsure, say Y.
+        If unsure, say N.
 
-config YAFFS_SHORT_NAMES_IN_RAM
-       bool "Cache short names in RAM"
+config YAFFS_XATTR
+       bool "Enable yaffs2 xattr support"
        depends on YAFFS_FS
        default y
        help
-         If this config is set, then short names are stored with the
-         yaffs_Object.  This costs an extra 16 bytes of RAM per object,
-         but makes look-ups faster.
-
-         If unsure, say Y.
+        If this is set then yaffs2 will provide xattr support.
+        If unsure, say Y.