X-Git-Url: http://www.aleph1.co.uk/gitweb/?p=yaffs2.git;a=blobdiff_plain;f=Kconfig;h=dd330790c2501c723e2cccb5b36059d5e7b90e51;hp=da516ddbc060478e1f50475576782492b6bfd1e3;hb=2ae22f05374b4cb19202ddaac9fc47458c732f0d;hpb=831a8e85fb344ae8ef092fe12627e518d63fc009

diff --git a/Kconfig b/Kconfig
index da516dd..dd33079 100644
--- a/Kconfig
+++ b/Kconfig
@@ -5,6 +5,7 @@
 config YAFFS_FS
 	tristate "YAFFS2 file system support"
 	default n
+	depends on MTD
 	select YAFFS_YAFFS1
 	select YAFFS_YAFFS2
 	help
@@ -58,15 +59,85 @@ config YAFFS_YAFFS2
 
 	  If unsure, say Y.
 
-config YAFFS_DISABLE_CHUNK_ERASED_CHECK
-	bool "Turn off debug chunk erase check"
-	depends on YAFFS_FS
+config YAFFS_AUTO_YAFFS2
+	bool "Autoselect yaffs2 format"
+	depends on YAFFS_YAFFS2
 	default y
 	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.
+	  Without this, you need to explicitely use yaffs2 as the file
+	  system type. With this, you can say "yaffs" and yaffs or yaffs2
+          will be used depending on the device page size.
+
+	  If unsure, say Y.
+
+config YAFFS_DISABLE_LAZY_LOAD
+	bool "Disable lazy loading"
+	depends on YAFFS_YAFFS2
+	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.
+
+	  Setting this to 'y' will disable lazy loading.
+
+	  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
+	default n
+	help
+	  Wide tnodes are only used for large 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 make
+	  large arrays slower.
+
+	  If unsure, say N.
+
+config YAFFS_ALWAYS_CHECK_CHUNK_ERASED
+	bool "Force chunk erase check"
+	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.
+
+	  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.