trezor-firmware

Commit Graph

Author	SHA1	Message	Date
matejcik	3789a3372b	core/sdcard: modify exception handling in fatfs expose ff.c constants, raise them as arguments to FatFSError introduce NotMounted and NoFilesystem as subclasses of FatFSError with the appropriate error code set	4 years ago
matejcik	9ab84d2455	core/tests: thoroughly test modified APIs	4 years ago
matejcik	fa746e2990	core/fatfs: rework low-level FatFS API Instead of having possibly multiple FatFS objects, each with its own `fs` struct, there is one global static fs_instance. This is to match the mode of operation of ff.c, which assumes a global list of mounts, and all functions operate on the global based on path. Methods of FatFS were converted to functions on the fatfs module. fatfs.unmount() does not call ff.c's unmount, but simply invalidates fs_instance. This is basically what ff.c would do, except without messing with ff.c's global list of mounts.	4 years ago

Author

SHA1

Message

Date

matejcik

3789a3372b

core/sdcard: modify exception handling in fatfs

expose ff.c constants, raise them as arguments to FatFSError

introduce NotMounted and NoFilesystem as subclasses of FatFSError with
the appropriate error code set

matejcik

9ab84d2455

core/tests: thoroughly test modified APIs

matejcik

fa746e2990

core/fatfs: rework low-level FatFS API

Instead of having possibly multiple FatFS objects, each with its own
`fs` struct, there is one global static fs_instance. This is to match
the mode of operation of ff.c, which assumes a global list of mounts,
and all functions operate on the global based on path.

Methods of FatFS were converted to functions on the fatfs module.

fatfs.unmount() does not call ff.c's unmount, but simply invalidates
fs_instance. This is basically what ff.c would do, except without
messing with ff.c's global list of mounts.

3 Commits (7ce4e13bcf36a0db24672ae44055ae4b30366681)