ncch_container: Add support for exheader replacement #4813
Merged
Conversation
This file contains 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
wwylele
reviewed
Jun 30, 2019
wwylele
previously approved these changes
Jun 30, 2019
wwylele
reviewed
Jun 30, 2019
B3n30
approved these changes
Jun 30, 2019
wwylele
approved these changes
Jun 30, 2019
zhaowenlan1779
approved these changes
Jul 6, 2019
This adds support for custom exheaders, which brings feature parity with Luma3DS's code patching functionality and allows for injecting new game code.
FearlessTobi
approved these changes
Jul 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds support for custom exheaders, which brings feature parity
with Luma3DS's code patching functionality and allows for injecting
new game code.
Also, resize the code buffer according to the exheader to make it possible
to increase code size by combining exheader replacement and
IPS patching.
This also ensures the codeset memory (created in
AppLoader_NCCH::LoadExec) actually is large enough.
This change is