-
Notifications
You must be signed in to change notification settings - Fork 638
vector: specify CAN FD support in config detection #641
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
Conversation
Co-Authored-By: Felix Divo <felixdivo@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## develop #641 +/- ##
===========================================
+ Coverage 63.89% 65.66% +1.76%
===========================================
Files 66 65 -1
Lines 5955 5717 -238
===========================================
- Hits 3805 3754 -51
+ Misses 2150 1963 -187 |
Codecov Report
@@ Coverage Diff @@
## develop #641 +/- ##
===========================================
+ Coverage 63.46% 63.62% +0.15%
===========================================
Files 66 66
Lines 6016 6001 -15
===========================================
Hits 3818 3818
+ Misses 2198 2183 -15 |
does the bitshift |
Yeah, I guess. (See here) |
I can only merge this is the formatter approves. @jsee23 Could you fix this? |
Skip any channels that don't have support for CAN (ex. LIN, Digital/Analog IO) instead of accepting everything when using auto-detection. Note: This is a backport of hardbyte#641 to 3.3.4 Addresses hardbyte#908
This adds the CAN FD support in the config detection for Vector. Additionally, channels without CAN support are skipped.
dict entry is aligned with PCAN backend, see #640.