FBT/SDK: New app flag UnloadAssetPacks to free RAM #260
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
Willy-JL
requested review from
Sil333033,
HaxSam and
MatthewKuKanich
as code owners
|
Compiled f7 firmware for commit
|
feb-kj
approved these changes
Oct 24, 2024
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.
Suggestion cannot be applied right now. Please check back later.
What's new
flags=["UnloadAssetPacks"],inapplication.famto request unload active asset pack, therefore freeing RAM.fapmetaELF section, 1 byte larger to store flags data, but backwards compatible both ways (checks for smaller OFW manifest and loads it correctly, and when this larger manifest is laoded by other firmwares it overflows 1 byte into padding memory ofFlipperApplicationstruct since manifest struct is 85 bytes, padded to 88 for alignment)For the reviewer