IEEE 802.15.4 Updates for Kernel Ring Buffer #376
Merged
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
ppannuto
approved these changes
Mar 20, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
|
Looks like this PR failed when running the final checks before merging. @ppannuto should we run the CI again or was this due to some actual issue? |
bradjc
changed the title
Looks like some weird (hopefully transient) infra error — trying again..
|
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.
This PR updates the libtock-c 15.4 functions to use the receive ring buffer the kernel now expects. I updated the relevant 15.4 libtock functions in addition to the various test apps. Additionally, I attempted to update logic using hard coded values for the frame meta data length.
The test apps are currently operating as expected with these changes.