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
Virtual filesystem support broken on baremetal targets #3460
Comments
Now that we have all these processors with flash support, I think I am feeling the pain of this issue.
|
What can I do to help resolve this @bgould ? |
@bgould I think I need some help to understand how to fix this, if you please. |
LittleFS filesystem is working with onboard flash using the latest |
However, FAT filesystem is still broken, which was perhaps not clear from my previous comment. |
@bgould I need your help to figure out what to fix, and where. 😿 How is it possible that LittleFS is still working but FatFS not? I am very confused. |
@deadprogram @bgould Heads up to both of y'all, I'm writing a FatFS port in pure Go |
As best I can tell, virtual filesystem support on baremetal targets was effectively removed by a680bfb
NewFile in src/os/file_other.go always returns a stdioFileHandle now (a680bfb#diff-639e6d3c80d353b492953bcbd0b3eec979e6c88a776684acd1ac961b6217e24eR36) and should be refactored to delegate a mounted virtual filesystem if it exists.
The text was updated successfully, but these errors were encountered: