summaryrefslogtreecommitdiff
path: root/nuttx/drivers/mtd/README.txt
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2013-12-04 16:41:45 -0600
committerGregory Nutt <gnutt@nuttx.org>2013-12-04 16:41:45 -0600
commit1077db9bc326ffdebacf9589393f085c2b8e7755 (patch)
treec2075d32d25507b262c9500e8722717817a85a85 /nuttx/drivers/mtd/README.txt
parentedc43a08908d200d5aa88c7a78f0dd94e5bac3aa (diff)
downloadpx4-nuttx-1077db9bc326ffdebacf9589393f085c2b8e7755.tar.gz
px4-nuttx-1077db9bc326ffdebacf9589393f085c2b8e7755.tar.bz2
px4-nuttx-1077db9bc326ffdebacf9589393f085c2b8e7755.zip
Cosmetic updates to comments and READMEs
Diffstat (limited to 'nuttx/drivers/mtd/README.txt')
-rw-r--r--nuttx/drivers/mtd/README.txt11
1 files changed, 7 insertions, 4 deletions
diff --git a/nuttx/drivers/mtd/README.txt b/nuttx/drivers/mtd/README.txt
index ea7bcfbde..76498096b 100644
--- a/nuttx/drivers/mtd/README.txt
+++ b/nuttx/drivers/mtd/README.txt
@@ -123,11 +123,12 @@ NAND MEMORY
SMART FS
--------
- I have not yet tried SmartFS. But I know that it does not perform bad
- block checking (like FAT). I do not know if it assumes that it can write
- into erased regions of a sector multiple times (like NXFFS).
+ I have not yet tried SmartFS. It does support some wear-leveling
+ similar to NXFFS, but like FAT, cannot handle bad blocks and like NXFFS,
+ it will try to re-write erased bits. So SmartFS is not really an
+ option either.
- What is Needed
+ What is Needed
--------------
What is needed to work with FAT properly would be another MTD layer
@@ -136,3 +137,5 @@ NAND MEMORY
on top of the NAND.
Another, less general, option would be support bad blocks within FAT.
+ Such a solution migh be possible for SLC NAND, but would not be
+ sufficiently general for all NAND types.