Update for Linux 2.6.19 support

[yaffs2.git] / Kconfig

diff --git a/Kconfig b/Kconfig
index f314f60073880ae0b72c226d7845ded6380dbc09..dd330790c2501c723e2cccb5b36059d5e7b90e51 100644 (file)
--- a/Kconfig
+++ b/Kconfig
@@ -90,6 +90,24 @@ config YAFFS_DISABLE_LAZY_LOAD
 
          If unsure, say N.
 
+config YAFFS_CHECKPOINT_RESERVED_BLOCKS
+       int "Reserved blocks for checkpointing"
+       depends on YAFFS_YAFFS2
+       default 10
+       help
+         Give the number of Blocks to reserve for checkpointing. These Blocks
+         are reserved per partition, so if you have very small partitions the
+         default (10) may be a mess for you. 
+         You can set this value to 0, but that does not mean checkpointing is
+         disabled at all. There only won't be any specially reserved blocks for
+         checkpointing, so if there is enough free space on the filesystem,
+         it will be used for checkpointing.
+
+         If unsure, leave at default (10), but don't wonder if there are always
+         2MB used on your large page device partition (10 x 2k pagesize). When
+         using small partitions or when being very small on space, you probably
+         want to set this to zero.
+
 config YAFFS_DISABLE_WIDE_TNODES
        bool "Turn off wide tnodes"
        depends on YAFFS_FS
@@ -105,15 +123,21 @@ config YAFFS_DISABLE_WIDE_TNODES
 
          If unsure, say N.
 
-config YAFFS_DISABLE_CHUNK_ERASED_CHECK
-       bool "Turn off debug chunk erase check"
+config YAFFS_ALWAYS_CHECK_CHUNK_ERASED
+       bool "Force chunk erase check"
        depends on YAFFS_FS
-       default y
+       default n
        help
-         Enabling this turns off the test that chunks are erased in flash
-         before writing to them.  This is safe, since the write verification
-         will fail.  Suggest enabling the test (ie. say N)
-         during development to help debug things.
+          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.
+
+         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.
+ 
+         Suggest setting Y during development and ironing out driver issues
+         etc. Suggest setting to N if you want faster writing.                  
 
          If unsure, say Y.