summaryrefslogtreecommitdiff
path: root/fs/Kconfig
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2007-07-11 17:23:54 +0400
committerDavid Woodhouse <dwmw2@infradead.org>2007-07-11 17:23:54 +0400
commita6bc432e296dfa1f05d4b586ca5ca3085a2d42d7 (patch)
treedb51669fcc74686efb4c65f98938907d76202ffa /fs/Kconfig
parentef53cb02ffee8ceb44ea75f778f77eace6b9c89a (diff)
downloadlinux-a6bc432e296dfa1f05d4b586ca5ca3085a2d42d7.tar.xz
[JFFS2] Add support for write-buffer verification.
We've seen some evil corruption issues, where the corruption seems to be introduced after the JFFS2 crc32 is calculated but before the NAND controller calculates the ECC. So it's in RAM or in the PCI DMA transfer; not on the flash. Attempt to catch it earlier by (optionally) reading back from the flash immediately after writing it. Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'fs/Kconfig')
-rw-r--r--fs/Kconfig8
1 files changed, 8 insertions, 0 deletions
diff --git a/fs/Kconfig b/fs/Kconfig
index e9c5b81dd665..e19423a2aa7d 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -1228,6 +1228,14 @@ config JFFS2_FS_WRITEBUFFER
- NOR flash with transparent ECC
- DataFlash
+config JFFS2_FS_WBUF_VERIFY
+ bool "Verify JFFS2 write-buffer reads"
+ depends on JFFS2_FS_WRITEBUFFER
+ default n
+ help
+ This causes JFFS2 to read back every page written through the
+ write-buffer, and check for errors.
+
config JFFS2_SUMMARY
bool "JFFS2 summary support (EXPERIMENTAL)"
depends on JFFS2_FS && EXPERIMENTAL