Kconfig 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171
  1. #
  2. # yaffs file system configurations
  3. #
  4. config YAFFS_FS
  5. tristate "yaffs2 file system support"
  6. default n
  7. depends on MTD_BLOCK
  8. select YAFFS_YAFFS1
  9. select YAFFS_YAFFS2
  10. help
  11. yaffs2, or Yet Another Flash File System, is a file system
  12. optimised for NAND Flash chips.
  13. To compile the yaffs2 file system support as a module, choose M
  14. here: the module will be called yaffs2.
  15. If unsure, say N.
  16. Further information on yaffs2 is available at
  17. <http://www.aleph1.co.uk/yaffs/>.
  18. config YAFFS_YAFFS1
  19. bool "512 byte / page devices"
  20. depends on YAFFS_FS
  21. default y
  22. help
  23. Enable yaffs1 support -- yaffs for 512 byte / page devices
  24. Not needed for 2K-page devices.
  25. If unsure, say Y.
  26. config YAFFS_9BYTE_TAGS
  27. bool "Use older-style on-NAND data format with pageStatus byte"
  28. depends on YAFFS_YAFFS1
  29. default n
  30. help
  31. Older-style on-NAND data format has a "pageStatus" byte to record
  32. chunk/page state. This byte is zero when the page is discarded.
  33. Choose this option if you have existing on-NAND data using this
  34. format that you need to continue to support. New data written
  35. also uses the older-style format. Note: Use of this option
  36. generally requires that MTD's oob layout be adjusted to use the
  37. older-style format. See notes on tags formats and MTD versions
  38. in yaffs_mtdif1.c.
  39. If unsure, say N.
  40. config YAFFS_DOES_ECC
  41. bool "Lets yaffs do its own ECC"
  42. depends on YAFFS_FS && YAFFS_YAFFS1 && !YAFFS_9BYTE_TAGS
  43. default n
  44. help
  45. This enables yaffs to use its own ECC functions instead of using
  46. the ones from the generic MTD-NAND driver.
  47. If unsure, say N.
  48. config YAFFS_ECC_WRONG_ORDER
  49. bool "Use the same ecc byte order as Steven Hill's nand_ecc.c"
  50. depends on YAFFS_FS && YAFFS_DOES_ECC && !YAFFS_9BYTE_TAGS
  51. default n
  52. help
  53. This makes yaffs_ecc.c use the same ecc byte order as Steven
  54. Hill's nand_ecc.c. If not set, then you get the same ecc byte
  55. order as SmartMedia.
  56. If unsure, say N.
  57. config YAFFS_YAFFS2
  58. bool "2048 byte (or larger) / page devices"
  59. depends on YAFFS_FS
  60. default y
  61. help
  62. Enable yaffs2 support -- yaffs for >= 2K bytes per page devices
  63. If unsure, say Y.
  64. config YAFFS_AUTO_YAFFS2
  65. bool "Autoselect yaffs2 format"
  66. depends on YAFFS_YAFFS2
  67. default y
  68. help
  69. Without this, you need to explicitely use yaffs2 as the file
  70. system type. With this, you can say "yaffs" and yaffs or yaffs2
  71. will be used depending on the device page size (yaffs on
  72. 512-byte page devices, yaffs2 on 2K page devices).
  73. If unsure, say Y.
  74. config YAFFS_DISABLE_TAGS_ECC
  75. bool "Disable yaffs from doing ECC on tags by default"
  76. depends on YAFFS_FS && YAFFS_YAFFS2
  77. default n
  78. help
  79. This defaults yaffs to using its own ECC calculations on tags instead of
  80. just relying on the MTD.
  81. This behavior can also be overridden with tags_ecc_on and
  82. tags_ecc_off mount options.
  83. If unsure, say N.
  84. config YAFFS_ALWAYS_CHECK_CHUNK_ERASED
  85. bool "Force chunk erase check"
  86. depends on YAFFS_FS
  87. default n
  88. help
  89. Normally yaffs only checks chunks before writing until an erased
  90. chunk is found. This helps to detect any partially written
  91. chunks that might have happened due to power loss.
  92. Enabling this forces on the test that chunks are erased in flash
  93. before writing to them. This takes more time but is potentially
  94. a bit more secure.
  95. Suggest setting Y during development and ironing out driver
  96. issues etc. Suggest setting to N if you want faster writing.
  97. If unsure, say Y.
  98. config YAFFS_EMPTY_LOST_AND_FOUND
  99. bool "Empty lost and found on boot"
  100. depends on YAFFS_FS
  101. default n
  102. help
  103. If this is enabled then the contents of lost and found is
  104. automatically dumped at mount.
  105. If unsure, say N.
  106. config YAFFS_DISABLE_BLOCK_REFRESHING
  107. bool "Disable yaffs2 block refreshing"
  108. depends on YAFFS_FS
  109. default n
  110. help
  111. If this is set, then block refreshing is disabled.
  112. Block refreshing infrequently refreshes the oldest block in
  113. a yaffs2 file system. This mechanism helps to refresh flash to
  114. mitigate against data loss. This is particularly useful for MLC.
  115. If unsure, say N.
  116. config YAFFS_DISABLE_BACKGROUND
  117. bool "Disable yaffs2 background processing"
  118. depends on YAFFS_FS
  119. default n
  120. help
  121. If this is set, then background processing is disabled.
  122. Background processing makes many foreground activities faster.
  123. If unsure, say N.
  124. config YAFFS_DISABLE_BAD_BLOCK_MARKING
  125. bool "Disable yaffs2 bad block marking"
  126. depends on YAFFS_FS
  127. default n
  128. help
  129. Useful during early flash bring up to prevent problems causing
  130. lots of bad block marking.
  131. If unsure, say N.
  132. config YAFFS_XATTR
  133. bool "Enable yaffs2 xattr support"
  134. depends on YAFFS_FS
  135. default y
  136. help
  137. If this is set then yaffs2 will provide xattr support.
  138. If unsure, say Y.