mulle: Initialize xtimer early to support nvram usage in board_init #4133
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jnohlgard
added
Type: bug
|
Seems reasonable. I need to trust you in that. ACK and go |
PeterKietzmann
added a commit
that referenced
this pull request
Oct 22, 2015
mulle: Initialize xtimer early to support nvram usage in board_init
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
xtimer_init is normally run by auto_init, but that runs after board_init and we want to use nvram_spi inside board_init. Mulle is currently broken in master, error introduced by me in #3485 (there used to be a hwtimer_init inside board_init before, but it went away during some rebase)
Tested working on mulle.