Remove save uEnv.txt to filesystem #31
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
The firsboot reads detected console from uEnv for now and it needs to be changed beforehand there. There is however issue with current fatload/fatwrite cmd and they kinda messup either writing eEnv.txt (garbled txt) or reading console variant (thus TriForceX/MiyooCFW#647), so the endgoal would be to not use both. Maybe switching to ext4 would solve at least load/write in memory. |
Member
Author
|
Yes, I know about that, this was the reason to create this PR. Only firstboot script is using this file, kernel is loading from dedicated module MiyooCFW/kernel#83 Firstboot script could also use it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove save uEnv.txt to the filesystem to avoid data corruption