Linker tweaks to place vital PicoDVI library funcs in RAM #1541
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
Linker tweaks for RAM-resident PicoDVI library functions
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.
As discussed in previous issue (which I’ll go close in a moment), adjustments to linker script to place certain code in RAM, required for PicoDVI library when used in combination with flash-writing code (e.g. filesystem).
If you’d prefer, I could go through PicoDVI.cpp and dvi.c and extensively decorate all functions there as not-in-flash (so they could then be removed here), but regardless this is still going to require *interp.c.obj *divider.S.obj in the linker script.
For non-PicoDVI projects, interp and divider are obscure and/or small such that they’ll have minimal or no impact on RAM.