Block Upload and Transmit Queue Refactoring#39
Merged
Conversation
Instead, let NodeMbox handle outgoing messages as well. This allows re-using the buffer used for SDO block receive for block transmission, allows zencan to determine how large of a buffer is required (this is fairly estimatable based on number of PDOs, SDO servers, etc), and allows for a more flexible "pull" option, where a CAN controller interrupt can grab messages as slots available while I think not restricting use cases -- an application can always poll the NodeMbox after every process call.
mcbridejc
force-pushed
the
transmit-queue
branch
from
d2b6d8f to
e0a59f5
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
zencan-node/README.mdso there's less docs to keep up to date.