github-mirrors/thirdparty-littlefs
1
0
Fork 0
mirror of https://github.com/eledio-devices/thirdparty-littlefs.git synced 2025-11-01 00:38:29 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #37 from jrast/patch-1

Browse Source 
Added a note about the callback functions
This commit is contained in:
Christopher Haster
2018-03-13 00:13:44 -05:00
committed by GitHub
parent 155224600a f72f6d6a05
commit 58f3bb1f08
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@@ -115,10 +115,17 @@ All littlefs have the potential to return a negative error code. The errors
can be either one of those found in the `enum lfs_error` in [lfs.h](lfs.h), can be either one of those found in the `enum lfs_error` in [lfs.h](lfs.h),
or an error returned by the user's block device operations. or an error returned by the user's block device operations.
It should also be noted that the current implementation of littlefs doesn't In the configuration struct, the `prog` and `erase` function provided by the
really do anything to ensure that the data written to disk is machine portable. user may return a `LFS_ERR_CORRUPT` error if the implementation already can
This is fine as long as all of the involved machines share endianness detect corrupt blocks. However, the wear leveling does not depend on the return
(little-endian) and don't have strange padding requirements. code of these functions, instead all data is read back and checked for
integrity.
If your storage caches writes, make sure that the provided `sync` function
flushes all the data to memory and ensures that the next read fetches the data
from memory, otherwise data integrity can not be guaranteed. If the `write`
function does not perform caching, and therefore each `read` or `write` call
hits the memory, the `sync` function can simply return 0.
## Reference material ## Reference material