Home
last modified time | relevance | path

Searched refs:littlefs (Results 1 – 10 of 10) sorted by relevance

/third_party/littlefs/
DREADME.md1 ## littlefs section
8 --|o |---| littlefs |
14 **Power-loss resilience** - littlefs is designed to handle random power
18 **Dynamic wear leveling** - littlefs is designed with flash in mind, and
19 provides wear leveling over dynamic blocks. Additionally, littlefs can
22 **Bounded RAM/ROM** - littlefs is designed to work with a small amount of
97 littlefs takes in a configuration structure that defines how the filesystem
103 The state of the littlefs is stored in the `lfs_t` type which is left up
108 Once mounted, the littlefs provides a full set of POSIX-like file and
121 All littlefs calls have the potential to return a negative error code. The
[all …]
DREADME.OpenSource3 "Name" : "littlefs",
8 "Upstream URL" : "https://github.com/littlefs-project/littlefs",
Dlittlefs.gni30 "//third_party/littlefs/lfs.c",
31 "//third_party/littlefs/lfs_util.c",
32 "//third_party/littlefs/bd/lfs_rambd.c",
36 "//third_party/littlefs",
37 "//third_party/littlefs/bd",
DSPEC.md1 ## littlefs technical specification
4 covers the technical details of how the littlefs is stored on disk for
6 design of the littlefs, for more info on how littlefs works check
12 --|o |---| littlefs |
20 - littlefs is a block-based filesystem. The disk is divided into an array of
27 block size), littlefs also uses a program block size and read block size.
31 - By default, all values in littlefs are stored in little-endian byte order.
35 Metadata pairs form the backbone of littlefs and provide a system for
196 So in littlefs, 32-bit tags describe every type of metadata. And this means
218 in big-endian (and is the only thing in littlefs stored in big-endian). This
[all …]
DDESIGN.md1 ## The design of littlefs
8 --|o |---| littlefs |
14 littlefs was originally built as an experiment to learn about filesystem design
19 This document covers the high-level design of littlefs, how it is different
25 The embedded systems littlefs targets are usually 32-bit microcontrollers with
227 ## littlefs section
229 So what does littlefs do?
256 This is the idea behind littlefs. At the sub-block level, littlefs is built
258 on the filesystem. At the super-block level, littlefs is a CObW tree of blocks
300 Metadata pairs are the backbone of littlefs. These are small, two block logs
[all …]
/third_party/littlefs/tests/
Dtest_evil.toml2 # happen during normal operation of littlefs
11 // create littlefs
33 // create littlefs
79 // create littlefs
127 // create littlefs
189 // create littlefs
215 // create littlefs
234 // create littlefs with child dir
264 // create littlefs with child dir
Dtest_paths.toml228 lfs_stat(&lfs, "littlefs", &info) => LFS_ERR_NOENT;
229 lfs_remove(&lfs, "littlefs") => LFS_ERR_NOENT;
231 lfs_mkdir(&lfs, "littlefs") => 0;
232 lfs_stat(&lfs, "littlefs", &info) => 0;
233 assert(strcmp(info.name, "littlefs") == 0);
235 lfs_remove(&lfs, "littlefs") => 0;
236 lfs_stat(&lfs, "littlefs", &info) => LFS_ERR_NOENT;
Dtest_move.toml987 // littlefs keeps files sorted, so we know the order these will be in
1133 // littlefs keeps files sorted, so we know the order these will be in
1289 // littlefs keeps files sorted, so we know the order these will be in
/third_party/NuttX/include/nuttx/fs/
Ddirent_fs.h301 void *littlefs; member
/third_party/NuttX/
DReleaseNotes20739 - LittleFS: Adds an initial port the ARM mbed littlefs to NuttX. This does
23279 - fs/littlefs/lfs.c: Fix lfs_format bug. In superblock disk root-
27074 - PR-851 Upgrade littlefs to v2.2.1
29482 * [#3137](https://github.com/apache/incubator-nuttx/pull/3137) fs/littlefs: Suppport the duplicatio…
30261 …* [#4330](https://github.com/apache/incubator-nuttx/pull/#4330) fs/littlefs: improve littlefs flas…