-
Notifications
You must be signed in to change notification settings - Fork 2k
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
sys/stdio_udp: add stdio over UDP #19081
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Two comments inline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a few nitpicks that I would be extremely happy if you could address them.
To avoid another round-trip, I already add an ACK.
The telnet module checks for |
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
👎 Rejected by PR status |
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
bors merge |
Already running a review |
Build succeeded: |
Contribution description
stdio_telnet
can sometimes be slow and also a bit heavy when TCP is otherwise not used.When doing remote debugging, a lost packet isn't usually so bad, so we don't need the reliability we get from telnet.
This adds a stdio via UDP module that can be used with
nc
orsocat
:Testing procedure
Enable the module in e.g.
gnrc_networking
:You will not see any output unless you connect to the instance from a 2nd terminal:
Issues/PRs references