-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow usage of rpmsg static freertos related api #168
Allow usage of rpmsg static freertos related api #168
Conversation
…se static api Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
3b55149
to
20692a1
Compare
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
Hi Dusan, let's target these changes for the next release (after v1.8.1 release), ok? Thanks. |
Hi @MichalPrincNXP , yes sure ;) |
#if ERPC_ALLOCATION_POLICY == ERPC_STATIC_POLICY |
Sure, will do |
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
Fixes pushed. Is that ok now? |
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
Update pushed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is linked with #169 and will be integrated together. Nevertheless, this does not allow static allocation of all erpc objects and the work on the static allocations needs to continue (information for others looking at this PR). "Known issues and limitations" section should be added into the wiki with following statement:
Static allocations controlled by the ERPC_ALLOCATION_POLICY config macro are not fully supported yet, i.e. not all erpc objects can be allocated statically now. It deals with the ongoing process and the full static allocations support will be added in the future.
Thank you for this effort! |
This change depends on nxp-mcuxpresso/rpmsg-lite#14