Replies: 2 comments 3 replies
-
Maybe make a new branch for it and put 'still in development. use at own risk' in the readme of that branch. And a suggestion to make frequent backups and use a fresh card for that fork. also, I wouldn't mess with the nand bc its too easy to mess it up and loose all your progress in all your games. |
Beta Was this translation helpful? Give feedback.
3 replies
-
I really need write support. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
should SD write support be enabled? it's only a few lines afaict and performance isn't too bad, but I'm afraid someone will end up messing the data in their card and blame us because "it's unstable and shouldn't be released yet" or something like that
even I'm somewhat afraid of toggling the wrong bit at the wrong time and having the whole FS corrupt itself
adding NAND support is also possible but out of the question right now - it's too dangerous and will end up bricking someone
if anyone knows any virtio people, maybe we should suggest adding a MMC device type? they have things that make them stand out from plain "block devices", like clock controls, sleep mode, switching between 1 and 4 bit mode, multiple voltage select, internal registers like the CID/CSD and other funky things that can cause the card to die (or be revived, if you have a locked NAND it could be unlocked directly from linux)
any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions