Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: mass storage with write support #7

Open
tyll opened this issue Jul 7, 2018 · 1 comment
Open

RFC: mass storage with write support #7

tyll opened this issue Jul 7, 2018 · 1 comment

Comments

@tyll
Copy link
Contributor

tyll commented Jul 7, 2018

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).

@xobs
Copy link
Member

xobs commented Jul 10, 2018

Making it a compile-time switch is probably easiest.

We can ship prebuilt versions of both the readonly and read/write version in the prebuilt/ directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants