-
Notifications
You must be signed in to change notification settings - Fork 17
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
Zephyr integration: Use K_HEAP_MEM_POOL_SIZE #23
Conversation
Could you confirm if it is compatible with legacy versions of Zephyr? |
@arnopo no, older Zephyr versions don't have a Btw, note that the discussion in zephyrproject-rtos/zephyr#65908 is still ongoing, so I would suggest to wait for a consensus to be reached there before merging this PR. |
There was sufficient consensus in today's Arch WG meeting on how to proceed, that I think this can be merged now. After that I'll update the main tree PR west.yml to reference the right commit. |
The zephyrproject-rtos/zephyr#65523 PR would need to be addressed first. the rebase on the v2023.10 released is blocked due to a test that fails |
@jhedberg : |
Done: OpenAMP/libmetal#280 |
This define should be used instead of the Kconfig option to determine if the k_malloc family of functions are available. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
f3f9214
to
f8b9547
Compare
@carlocaione : Please could you review OpenAMP/libmetal#280. Then I will merge it and create a PR to rebase the Zephyr libmetal module on top of. @jhedberg : I assume that you will update the west.yml in zephyrproject-rtos/zephyr#65908 then to integrate it, right? |
Correct. |
Closing, now that this has been superseded by #25 |
This define should be used instead of the Kconfig option to determine if the k_malloc family of functions are available.