2 # YAFFS file system configurations
5 tristate "Yet Another Flash Filing System(YAFFS) file system support"
7 YAFFS, for Yet Another Flash Filing System, is a filing system
8 optimised for NAND Flash chips.
10 To compile the YAFFS file system support as a module, choose M here:
11 the module will be called yaffs.
15 Further information on YAFFS is available at
16 <http://www.aleph1.co.uk/yaffs/>.
18 config YAFFS_MTD_ENABLED
19 bool "NAND mtd support"
22 This adds the yaffs file system support for working with a NAND mtd.
26 config YAFFS_RAM_ENABLED
27 bool "yaffsram file system support"
30 This adds the yaffsram file system support. Nice for testing on x86,
31 but uses 2MB of RAM. Don't enable for NAND-based targets.
35 comment "WARNING: mtd and/or yaffsram support should be selected"
36 depends on YAFFS_FS && !YAFFS_MTD_ENABLED && !YAFFS_RAM_ENABLED
38 config YAFFS_USE_OLD_MTD
39 bool "Old mtd support"
40 depends on YAFFS_FS && 0
42 Enable this to use the old MTD stuff that did not have yaffs support.
43 You can use this to get around compilation problems, but the best
44 thing to do is to upgrade your MTD support. You will get better speed.
48 config YAFFS_USE_NANDECC
49 bool "Use ECC functions of the generic MTD-NAND driver"
53 This enables the ECC functions of the generic MTD-NAND driver.
54 This will not work if you are using the old mtd.
56 NB Use NAND ECC does not work at present with yaffsram.
60 config YAFFS_ECC_WRONG_ORDER
61 bool "Use the same ecc byte order as Steven Hill's nand_ecc.c"
64 This makes yaffs_ecc.c use the same ecc byte order as
65 Steven Hill's nand_ecc.c. If not set, then you get the
66 same ecc byte order as SmartMedia.
70 config YAFFS_USE_GENERIC_RW
71 bool "Use Linux file caching layer"
75 Use generic_read/generic_write for reading/writing files. This
76 enables the use of the Linux file caching layer.
78 If you disable this, then caching is disabled and file read/write
83 config YAFFS_USE_HEADER_FILE_SIZE
84 bool "Use object header size"
87 When the flash is scanned, two file sizes are constructed:
88 * The size taken from the object header for the file.
89 * The size figured out by scanning the data chunks.
90 If this option is enabled, then the object header size is used,
91 otherwise the scanned size is used.
95 config YAFFS_DISABLE_CHUNK_ERASED_CHECK
96 bool "Turn off debug chunk erase check"
100 Enabling this turns off the test that chunks are erased in flash
101 before writing to them. This is safe, since the write verification
102 will fail. Suggest enabling the test (ie. say N)
103 during development to help debug things.
107 #config YAFFS_DISABLE_WRITE_VERIFY
108 # bool "Disable write verify (DANGEROUS)"
109 # depends on YAFFS_FS && EXPERIMENTAL
111 # I am severely reluctant to provide this config. Disabling the
112 # verification is not a good thing to do since NAND writes can
113 # fail silently. Disabling the write verification will cause your
114 # teeth to rot, rats to eat your corn and give you split ends.
115 # You have been warned. ie. Don't uncomment the following line.
120 config YAFFS_SHORT_NAMES_IN_RAM
121 bool "Cache short names in RAM"
125 If this config is set, then short names are stored with the
126 yaffs_Object. This costs an extra 16 bytes of RAM per object,
127 but makes look-ups faster.