littlefs2
littlefs2 copied to clipboard
Idiomatic Rust API for littlefs
Iteration over a directory is not very efficient, as it can't be safely paused and resumed. This leads to issues. For example in trussed, as a consequence the iteration happens...
Hi, I'm trying to setup littlefs2-sys crate but got this weird error on compile ( cargo:rustc-link-lib=static=lfs-sys cargo:rustc-link-search=native=/home/rust/rust-esp32-std-demo/target/xtensa-esp32-espidf/debug/build/littlefs2-sys-bfcc464d6158cf54/out --- stderr thread 'main' panicked at 'a libclang shared library is not loaded...
Hi, just discovered this lib. Seems like something very useful for storing data on an sd card on a microcontroller. When I try to add this library to a `no_std`...
Hi hi, thanks for making a neat thing ^_^ I'm about to use littlefs in a project and I was just wondering whether there are outstanding issues / what you're...
There seems to be some flexibility in what can be done while iterating over a directory, for instance the current file can be read, and it can even be deleted....
The `path::{Filename,Path}` objects are not very well-developed yet. I am aware of the following issues: - It would be nice to use `heapless::Vec` for paths, and handle back and forth...
Originally reported in #3. This ticket includes an example that can be run on x86_64 and instrumented with LLVM AddressSanitizer. ### STR ``` rust use core::mem; use littlefs2::{ consts, driver,...
UPDATE: Added Steps To Reproduce (STR) on x86_64 ### STR1 asan: `fs` and `File` clash ``` rust use littlefs2::{ consts, driver, fs::{File, Filesystem}, io::{Result, Write}, ram_storage, }; ram_storage!( name=RamStorage, backend=Ram,...
`test/ui/sync-fail.rs` shows how trying to close a file on a different filesystem fails at compile time. That compile time protection holds in that example because each filesystem instance has a...
Currently the user has to statically know the device size since `BLOCK_COUNT` is an associated constant. It would be useful if it would be possible to dynamically determine the device...