-
Notifications
You must be signed in to change notification settings - Fork 10
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
CAN: Initialisation Timeout #47
Conversation
b83fc2a
to
50a4bed
Compare
8709a8b
to
39bf2f8
Compare
I've now finally had another crack at this, as you will see. I noticed as I was adding a new event that the existing To preserve what looked like the existing behaviour (and what makes sense to me reading it), I now explicitly clear all three of the events, two of which were being implicitly cleared by the call to |
2f3df3f
to
68d36f5
Compare
CAN: correct callback CAN: move timer to context
68d36f5
to
9623764
Compare
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.
Looks good, thanks for the update. Just got a very minor suggestion.
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.
Looks good, thanks for the update.
Add an (optional) timeout on CAN initialisation.