Generalize the scheduler beyond timers #680
Closed
Conversation
This file contains hidden or 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
niaow
force-pushed
the
scheduler
branch
2 times, most recently
from
e907ba9 to
d74419a
Compare
Member
Author
|
Blocked on #710, which is the cause of the current CI failures. |
Member
Author
|
Rebased. |
aykevl
reviewed
Dec 8, 2019
Member
Author
|
I am basically going to need to redo this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This pull request begins the migration to the design discussed in #620 - moving the scheduler to a structure which allows anything to be used as a source of wakeups. For compatibility, the old scheduler timing components have been wrapped and put in a seperate file. As we implement fully correct functionality on various boards, we can exclude this temporary workaround with build tags.