mirror of
https://github.com/eledio-devices/thirdparty-littlefs.git
synced 2025-11-01 16:14:13 +01:00
Compare commits
2 Commits
v1.7.0
...
readme-upd
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
bad02b6003 | ||
|
|
0d7ae0fef4 |
@@ -182,6 +182,7 @@ jobs:
|
|||||||
-d "{
|
-d "{
|
||||||
\"tag_name\": \"$LFS_VERSION\",
|
\"tag_name\": \"$LFS_VERSION\",
|
||||||
\"name\": \"${LFS_VERSION%.0}\",
|
\"name\": \"${LFS_VERSION%.0}\",
|
||||||
|
\"draft\": true,
|
||||||
\"body\": $(jq -sR '.' <<< "$CHANGES")
|
\"body\": $(jq -sR '.' <<< "$CHANGES")
|
||||||
}"
|
}"
|
||||||
fi
|
fi
|
||||||
|
|||||||
15
README.md
15
README.md
@@ -175,3 +175,18 @@ handy.
|
|||||||
[littlefs-js](https://github.com/geky/littlefs-js) - A javascript wrapper for
|
[littlefs-js](https://github.com/geky/littlefs-js) - A javascript wrapper for
|
||||||
littlefs. I'm not sure why you would want this, but it is handy for demos.
|
littlefs. I'm not sure why you would want this, but it is handy for demos.
|
||||||
You can see it in action [here](http://littlefs.geky.net/demo.html).
|
You can see it in action [here](http://littlefs.geky.net/demo.html).
|
||||||
|
|
||||||
|
[mklfs](https://github.com/whitecatboard/Lua-RTOS-ESP32/tree/master/components/mklfs/src) -
|
||||||
|
A command line tool built by the [Lua RTOS](https://github.com/whitecatboard/Lua-RTOS-ESP32)
|
||||||
|
guys for making littlefs images from a host PC. Supports Windows, Mac OS,
|
||||||
|
and Linux.
|
||||||
|
|
||||||
|
[SPIFFS](https://github.com/pellepl/spiffs) - Another excellent embedded
|
||||||
|
filesystem for NOR flash. As a more traditional logging filesystem with full
|
||||||
|
static wear-leveling, SPIFFS will likely outperform littlefs on small
|
||||||
|
memories such as the internal flash on microcontrollers.
|
||||||
|
|
||||||
|
[Dhara](https://github.com/dlbeer/dhara) - An interesting NAND flash
|
||||||
|
translation layer designed for small MCUs. It offers static wear-leveling and
|
||||||
|
power-resilience with only a fixed O(|address|) pointer structure stored on
|
||||||
|
each block and in RAM.
|
||||||
|
|||||||
Reference in New Issue
Block a user