<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/extmod/fsusermount.h, branch encoding</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=encoding</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=encoding'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2017-01-30T01:26:08+00:00</updated>
<entry>
<title>extmod: Merge old fsusermount.h header into vfs.h and vfs_fat.h.</title>
<updated>2017-01-30T01:26:08+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2017-01-29T08:20:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=b697c890096805d9ccaf7553dbff5b82f5332609'/>
<id>urn:sha1:b697c890096805d9ccaf7553dbff5b82f5332609</id>
<content type='text'>
vfs.h is for generic VFS declarations, and vfs_fat.h is for VfsFat
specific things.
</content>
</entry>
<entry>
<title>py: Be more specific with MP_DECLARE_CONST_FUN_OBJ macros.</title>
<updated>2016-10-21T05:26:01+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-10-18T00:06:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=4ebdb1f2b217410cdc1cee0e0c0da8fceb7627f2'/>
<id>urn:sha1:4ebdb1f2b217410cdc1cee0e0c0da8fceb7627f2</id>
<content type='text'>
In order to have more fine-grained control over how builtin functions are
constructed, the MP_DECLARE_CONST_FUN_OBJ macros are made more specific,
with suffix of _0, _1, _2, _3, _VAR, _VAR_BETEEN or _KW.  These names now
match the MP_DEFINE_CONST_FUN_OBJ macros.
</content>
</entry>
<entry>
<title>esp8266/modous: Add os.umount method to unmount a filesystem.</title>
<updated>2016-08-26T02:45:21+00:00</updated>
<author>
<name>Radomir Dopieralski</name>
<email>openstack@sheep.art.pl</email>
</author>
<published>2016-08-22T14:10:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=d29ca28288581ca788e468528ea1680b99eb49e5'/>
<id>urn:sha1:d29ca28288581ca788e468528ea1680b99eb49e5</id>
<content type='text'>
This is an object-oriented approach, where uos is only a proxy for the
methods on the vfs object.  Some internals had to be exposed (the STATIC
keyword removed) for this to work.

Fixes #2338.
</content>
</entry>
<entry>
<title>extmod/vfs_fat: Object-oriented encapsulation of FatFs VFS.</title>
<updated>2016-02-14T17:15:21+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2016-02-13T20:51:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=e9be6a378c23ece54521fb9098fda028f6c7d88f'/>
<id>urn:sha1:e9be6a378c23ece54521fb9098fda028f6c7d88f</id>
<content type='text'>
This implements OO interface based on existing fsusermount code and with
minimal changes to it, to serve as a proof of concept of OO interface.

Examle of usage:

bdev = RAMFS(48)
uos.VfsFat.mkfs(bdev)
vfs = uos.VfsFat(bdev, "/ramdisk")
f = vfs.open("foo", "w")
f.write("hello!")
f.close()
</content>
</entry>
<entry>
<title>extmod/fsusermount: Move BP_IOCTL_xxx constants to fsusermount.h.</title>
<updated>2016-02-10T23:40:35+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-02-10T23:36:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=e372e83b3042cb48fbe5706522d92f7aa5404ae6'/>
<id>urn:sha1:e372e83b3042cb48fbe5706522d92f7aa5404ae6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>extmod/fsusermount: Support mounting of multiple block devices.</title>
<updated>2016-02-10T23:40:10+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-02-10T16:32:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=b33a7705966a743c5e4c0c3c3bb83e6d97b5e84d'/>
<id>urn:sha1:b33a7705966a743c5e4c0c3c3bb83e6d97b5e84d</id>
<content type='text'>
This patch adds support to fsusermount for multiple block devices
(instead of just one).  The maximum allowed is fixed at compile time by
the size of the fs_user_mount array accessed via MP_STATE_PORT, which
in turn is set by MICROPY_FATFS_VOLUMES.

With this patch, stmhal (which is still tightly coupled to fsusermount)
is also modified to support mounting multiple devices   And the flash and
SD card are now just two block devices that are mounted at start up if
they exist (and they have special native code to make them more
efficient).
</content>
</entry>
<entry>
<title>extmod/fsusermount: Expose umount as a public function.</title>
<updated>2016-02-10T23:40:10+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-02-10T16:28:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=0e0ce47e65f4c1c57c9d23ba86d731b71d90346c'/>
<id>urn:sha1:0e0ce47e65f4c1c57c9d23ba86d731b71d90346c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>extmod/fsusermount: Change block protocol to support ioctl method.</title>
<updated>2016-02-10T08:59:31+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-02-09T14:28:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c33ad60a676d46cb18883beedd6c383d6fae9dd8'/>
<id>urn:sha1:c33ad60a676d46cb18883beedd6c383d6fae9dd8</id>
<content type='text'>
The new block protocol is:
- readblocks(self, n, buf)
- writeblocks(self, n, buf)
- ioctl(self, cmd, arg)

The new ioctl method handles the old sync and count methods, as well as
a new "get sector size" method.

The old protocol is still supported, and used if the device doesn't have
the ioctl method.
</content>
</entry>
<entry>
<title>extmod/fsusermount: Introduce separate mkfs() function.</title>
<updated>2016-02-09T22:50:07+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2016-02-09T22:50:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=5b85a86ce3aaabac49083e2699c90d011a1e4de3'/>
<id>urn:sha1:5b85a86ce3aaabac49083e2699c90d011a1e4de3</id>
<content type='text'>
Per the previously discussed plan. mount() still stays backward-compatible,
and new mkfs() is rought and takes more args than needed. But is a step
in a forward direction.
</content>
</entry>
<entry>
<title>extmod: Move fsusermount.c from stmhal for cross-port reuse.</title>
<updated>2015-11-25T11:19:36+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2015-11-24T22:43:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=3a1bbcc2ef46bbab90ef3cde88dfcd8810e71d74'/>
<id>urn:sha1:3a1bbcc2ef46bbab90ef3cde88dfcd8810e71d74</id>
<content type='text'>
</content>
</entry>
</feed>
