Home
last modified time | relevance | path

Searched refs:disk (Results 1 – 11 of 11) sorted by relevance

/littlefs-3.7.0-3.6.0/bd/
Dlfs_emubd.c132 bd->disk = NULL; in lfs_emubd_create()
135 bd->disk = malloc(sizeof(lfs_emubd_disk_t)); in lfs_emubd_create()
136 if (!bd->disk) { in lfs_emubd_create()
140 bd->disk->rc = 1; in lfs_emubd_create()
141 bd->disk->scratch = NULL; in lfs_emubd_create()
144 bd->disk->fd = open(bd->cfg->disk_path, in lfs_emubd_create()
147 bd->disk->fd = open(bd->cfg->disk_path, in lfs_emubd_create()
150 if (bd->disk->fd < 0) { in lfs_emubd_create()
159 bd->disk->scratch = malloc(bd->cfg->erase_size); in lfs_emubd_create()
160 if (!bd->disk->scratch) { in lfs_emubd_create()
[all …]
Dlfs_emubd.h155 lfs_emubd_disk_t *disk; member
/littlefs-3.7.0-3.6.0/
DREADME.md189 - [SPEC.md](SPEC.md) - The on-disk specification of littlefs with all the
234 - [littlefs-disk-img-viewer] - A memory-efficient web application for viewing
235 littlefs disk images in your web browser.
262 [littlefs-disk-img-viewer]: https://github.com/tniessen/littlefs-disk-img-viewer
DSPEC.md3 This is the technical specification of the little filesystem with on-disk
5 is stored on disk for introspection and tooling. This document assumes you are
20 - littlefs is a block-based filesystem. The disk is divided into an array of
40 are not necessarily sequential and may be anywhere on disk, so a "pointer" to a
359 Directories in littlefs are stored on disk as a linked-list of metadata pairs,
451 Associates the id with an on-disk data structure.
464 Directories in littlefs are stored on disk as a linked-list of metadata pairs,
837 program block size. However, the program block is not saved on disk, and can
838 change between mounts, so the FCRC size on disk may be different than the
Dlfs.c879 struct lfs_diskoff disk; member
897 struct lfs_diskoff disk = {0}; in lfs_dir_traverse() local
910 disk.block = dir->pair[0]; in lfs_dir_traverse()
911 disk.off = off+sizeof(lfs_tag_t); in lfs_dir_traverse()
912 buffer = &disk; in lfs_dir_traverse()
950 .disk = disk, in lfs_dir_traverse()
1068 disk = stack[sp-1].disk; in lfs_dir_traverse()
1426 const struct lfs_diskoff *disk = buffer; in lfs_dir_find_match() local
1432 disk->block, disk->off, name->name, diff); in lfs_dir_find_match()
1598 const struct lfs_diskoff *disk = buffer; in lfs_dir_commitattr() local
[all …]
DDESIGN.md21 low-level details covering every bit on disk, check out [SPEC.md](SPEC.md).
304 stored on disk. But remember that flash has limited write granularity. We can
327 disk v v
641 The additional pointers let us navigate the data-structure on disk much more
726 doesn't need to touch the disk, so the practical impact is minimal.
794 write data to disk, create copies
857 littlefs takes a cautious approach. Instead of trusting a free list on disk,
858 littlefs relies on the fact that the filesystem on disk is a mirror image of
859 the free blocks on the disk. The block allocator operates much like a garbage
891 complexity of managing on disk data structures, especially when handling
[all …]
/littlefs-3.7.0-3.6.0/scripts/
Dreadblock.py6 with open(args.disk, 'rb') as f:
Dreadtree.py17 with open(args.disk, 'rb') as f:
Dreadmdir.py343 with open(args.disk, 'rb') as f:
/littlefs-3.7.0-3.6.0/tests/
Dtest_alloc.toml460 // check that the disk isn't hurt
Dtest_dirs.toml778 // or on disk