You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to change the mass storage example to also allow write support with storing the actual changes in RAM. Since the RAM is quite limited in tomu, this would require to reduce the actual size of the mass storage device to a size that is not enough for a vfat filesystem. The current example implements a read-only vfat filesystem, though. Do you have any preference about how to implement this change? My idea was to make this conditional on a define so one can select to either get the current example or a fully working, quite slow mass-storage device (4 to 7 kiB probably).
The text was updated successfully, but these errors were encountered:
I would like to change the mass storage example to also allow write support with storing the actual changes in RAM. Since the RAM is quite limited in tomu, this would require to reduce the actual size of the mass storage device to a size that is not enough for a vfat filesystem. The current example implements a read-only vfat filesystem, though. Do you have any preference about how to implement this change? My idea was to make this conditional on a define so one can select to either get the current example or a fully working, quite slow mass-storage device (4 to 7 kiB probably).
The text was updated successfully, but these errors were encountered: