diff options
| author | Christopher Haster <chaster@utexas.edu> | 2018-03-13 05:27:05 +0300 |
|---|---|---|
| committer | Christopher Haster <chaster@utexas.edu> | 2018-03-13 05:27:39 +0300 |
| commit | f72f6d6a051ea048ded3bcd6ec638a13cfe40b02 (patch) | |
| tree | ec3d89dcd989f671989db0ff7263771126c8653c /README.md | |
| parent | 5c4ee2109de6aab794696c693ecb12e9791ea2d9 (diff) | |
Removed out of date note about endianness
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -115,11 +115,6 @@ 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), or an error returned by the user's block device operations. -It should also be noted that the current implementation of littlefs doesn't -really do anything to ensure that the data written to disk is machine portable. -This is fine as long as all of the involved machines share endianness -(little-endian) and don't have strange padding requirements. - In the configuration struct, the `prog` and `erase` function provided by the user may return a `LFS_ERR_CORRUPT` error if the implementation already can detect corrupt blocks. However, the wear leveling does not depend on the return |