summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorJim Mussared <jim.mussared@gmail.com>2019-12-16 12:38:27 +1100
committerJim Mussared <jim.mussared@gmail.com>2019-12-16 12:45:15 +1100
commitf3f7eb48da8bbd108e18103a45f9898846d6eb48 (patch)
treeb9d799c79b9e7db30f83085e7e2f7b7cab931bca
parentfb014155996c7568eb55ab06fdeaf6ff414f0280 (diff)
downloadmicropython-f3f7eb48da8bbd108e18103a45f9898846d6eb48.tar.gz
micropython-f3f7eb48da8bbd108e18103a45f9898846d6eb48.zip
docs/library/uos.rst: Clarify why the extended interface exists.
-rw-r--r--docs/library/uos.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/library/uos.rst b/docs/library/uos.rst
index 5505e6434f..bb7e491cce 100644
--- a/docs/library/uos.rst
+++ b/docs/library/uos.rst
@@ -234,6 +234,10 @@ methods (see below), in order to support a variety of use cases. A given block
device may implement one form or the other, or both at the same time. The second
form (with the offset parameter) is referred to as the "extended interface".
+Some filesystems (such as littlefs) that require more control over write
+operations, for example writing to sub-block regions without erasing, may require
+that the block device supports the extended interface.
+
.. class:: AbstractBlockDev(...)
Construct a block device object. The parameters to the constructor are