Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: thenickdude/asyncfatfs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 55a20a9888c0160fd0d8f943b49a0ead649d1076
Choose a base ref
..
head repository: thenickdude/asyncfatfs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6c2ef5f4c57d44ec7576da4c01e886a135e70d6a
Choose a head ref
Showing with 3 additions and 1 deletion.
  1. +3 −1 Readme.md
4 changes: 3 additions & 1 deletion Readme.md
Original file line number Diff line number Diff line change
@@ -85,7 +85,9 @@ set, `afatfs_poll()` will be called internally from the callback function provid
It is **strongly recommended** that `sdcard_readBlock()` and `sdcard_writeBlock()` implement some kind of scheduling
and never call the provided callback directly. Since the callback functions themselves will call `afatfs_poll()`
internally (in this mode), another call to any of the SD card primitives could be triggered. This will lead to
internally (in this mode), another call to any of the SD card primitives might be triggered. This will lead to
AsyncFatFS performing an unbounded amount of work (particularly at card init when writing the freefile) and using an
unbounded amount of stack size. If you have an infinite stack, then please go ahead. If not, then make sure that you
use the callbacks further up the stack, e.g. from your main loop.
Similarly, it is important that you update any internal state variables *before* you use any callback.