fixed useages of the hardware specific 0xE40000 address #625
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.
Removed usage of the
0xE40000
address from standard/common C functions (such asbzero
).boot_(v)snprintf
andboot_(v)asprintf
still use the0xE40000
address in their implementation. Which should be okay, since they are platform specific functions.Since
(v)snprintf
and(v)asprintf
are standard/common C functions, I have removed the option to have them link toboot_(v)snprintf
andboot_(v)asprintf
.