[GitHub] [incubator-nuttx] xiaoxiang781216 commented on pull request #6829: drivers/mtd:init commit of power-loss resilient cfg

[GitBox <gi...@apache.org>]

xiaoxiang781216 commented on PR #6829:
URL: https://github.com/apache/incubator-nuttx/pull/6829#issuecomment-1211103608

   > In general I'm a bit lost in architecture here. The MTD layer is designed to provide unified "continuous" access across the underlying physical layer, so I expect that all alignment or any other hardware related stuff is hidden "under" MTD device, but here I observe an opposite when the MTD caller handle alignment and other stuff. I mean that if MTD is implemented on top of flash that is what I expect, but not implementing a flash on top of MTD what I see here. I will submit a negative feedback until all design points are not clarified
   
   Basically, MTD like a block device(but need erase before write, wear leveling and ECC), which is hard to use from user application. To fix this problem, we normally have two approach:
   
   1. Build a complex filesystem on top of MTD to support a tree like structure(e.g. spiffs, smartfs and littlefs).
   2. Build a simple key value storage on top of MTD
   
   NVS(and cfgdata) is the second approach. @pkarashchenko do you get the idea?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org