-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
soc: espressif: esp32: fix SPIRAM allocation #74670
soc: espressif: esp32: fix SPIRAM allocation #74670
Conversation
Fixing the SPIRAM allocation by moving the output section before tha data is spilled in the generic output section. Signed-off-by: Marek Matej <[email protected]>
@LucasTambor @uLipe please review |
LGTM |
Keep this as DNM until we make sure it is all good (re-check). |
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. |
Is this still being worked on? |
Yeah, it is a part of a bigger picture. |
Glad to hear! Do you have a link to the PR or issue for the bigger picture? Will that work be done in time for Zephyr v3.7.1 (in 2 weeks)? |
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. |
@marekmatej is the DNM still appropriate? |
Yes, please. Some additional work will be added here. |
I'm closing this PR as #82870 takes care of ESP32 and ESP32-S3. |
Fixing the SPIRAM allocation by moving the output section before tha data is spilled in the generic output section.
The issue is described here: #74675