Skip to content

Commit b829645

Browse files
committed
BlockDevice design doc: TDBStore no longer requires flash simulation
1 parent bfbc188 commit b829645

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

storage/docs/BlockDevices/get_type_method.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,9 @@ To address this an add-on method of getting type is proposed for BlockDevice int
1515

1616
## The Motivation
1717

18-
Below there is a list of some examples to explain the motivation and the need for the adding of get_type to BlockDevice interface.
19-
20-
examples:
21-
- TDBStore needs to know if there are flash characteristics for the block device and if there aren�t it should use
22-
FlashSimBlockDevice to simulate a flash BlockDevice.
23-
- When creating a file system you would prefer working with FAT on top of SD while LITTLEFS on top of any flash block device.
24-
Those preference in favor of better performance.
18+
An example to explain the motivation and the need for the adding of get_type to BlockDevice interface:
19+
when creating a file system you would prefer working with FAT on top of SD while LITTLEFS on top of any flash block device.
20+
Those preferences are in favor of better performance.
2521

2622
To summarize the above, it may be very useful when using block device to know the type of the instance and especially, but not only,
2723
when using get_default_instace. Sometimes applications and tests would like to behave differently depending on the instance that has been created

0 commit comments

Comments
 (0)