Skip to content

Add Configurable LFN support to FatFS #316

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

Merged
merged 1 commit into from
Feb 22, 2014
Merged

Conversation

iabdalkader
Copy link
Contributor

No description provided.

@iabdalkader
Copy link
Contributor Author

dpgeorge added a commit that referenced this pull request Feb 22, 2014
Add Configurable LFN support to FatFS
@dpgeorge dpgeorge merged commit ed73fcd into micropython:master Feb 22, 2014
@dpgeorge
Copy link
Member

Apart from using up 512 bytes RAM (which is not too bad), I didn't enable LFN because of the issues with MS patents... anyone know the details of this??

@iabdalkader
Copy link
Contributor Author

I saw the note on the fatfs site, that's why they made it configurable, I think if it's configurable in MP too then it should be okay...

@dpgeorge
Copy link
Member

If it's not enabled, it might be okay. But I probably can't ship the boards with it compiled in...

@iabdalkader
Copy link
Contributor Author

It's a shame, those short upper case file names are so 80s :D

@dhylands
Copy link
Contributor

This article: http://www.geek.com/chips/clever-linux-folk-find-way-around-microsoft-fat-file-system-patent-824951/ seems to imply that you're only in violation of the patent if you store both the short and long filenames at the same time.

Linux seems to have sidestepped the patent by only storing the long variant of the filename.

@iabdalkader
Copy link
Contributor Author

in this case I vote enable LFN by default

@iabdalkader iabdalkader deleted the fatfs_lfn branch February 23, 2014 21:13
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

Successfully merging this pull request may close these issues.

3 participants