-
Notifications
You must be signed in to change notification settings - Fork 7.6k
linker: device_state : add alignment setting #86871
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
Conversation
the device_state need realocate when boot as second core. as the relocation does not know the alignment, this could be a case that the next data is mis-place after relocation. fix this by add a alignment in device_state section. still need revert aec0355 reported in zephyrproject-rtos#86871 fixes: zephyrproject-rtos#82841 Signed-off-by: Hake Huang <[email protected]>
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
the device_state need realocate when boot as second core. as the relocation does not know the alignment, this could be a case that the next data is mis-place after relocation. fix this by add a alignment in device_state section. still need revert aec0355 reported in zephyrproject-rtos#86871 fixes: zephyrproject-rtos#82841 Signed-off-by: Hake Huang <[email protected]>
|
the device_state need realocate when boot as second core. as the relocation does not know the alignment, this could be a case that the next data is mis-place after relocation. fix this by add a alignment in device_state section. still need revert aec0355 reported in zephyrproject-rtos#86871 fixes: zephyrproject-rtos#82841 Signed-off-by: Hake Huang <[email protected]>
the device_state need realocate when boot as second core.
as the relocation does not know the alignment, this could
be a case that the next data is mis-place after relocation.
fix this by add a alignment in device_state section.
still need revert aec0355
reported in #86871
fixes: #82841