Skip to content

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

Merged
merged 8 commits into from
Jul 19, 2019
Merged

vector: specify CAN FD support in config detection #641

merged 8 commits into from
Jul 19, 2019

Conversation

jsee23
Copy link
Contributor

@jsee23 jsee23 commented Jul 14, 2019

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.

Co-Authored-By: Felix Divo <felixdivo@users.noreply.github.com>
@codecov
Copy link

codecov bot commented Jul 15, 2019

Codecov Report

Merging #641 into develop will increase coverage by 1.76%.
The diff coverage is 0%.

@@             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
Copy link

codecov bot commented Jul 15, 2019

Codecov Report

Merging #641 into develop will increase coverage by 0.15%.
The diff coverage is 0%.

@@             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

@felixdivo felixdivo added this to the 4.0 Release milestone Jul 15, 2019
@zariiii9003
Copy link
Collaborator

does the bitshift XL_BUS_ACTIVE_CAP_CAN = (XL_BUS_TYPE_CAN << 16) return the same result as in C?

@felixdivo
Copy link
Collaborator

does the bitshift XL_BUS_ACTIVE_CAP_CAN = (XL_BUS_TYPE_CAN << 16) return the same result as in C? (@zariiii9003)

Yeah, I guess. (See here)

@felixdivo
Copy link
Collaborator

I can only merge this is the formatter approves. @jsee23 Could you fix this?

@felixdivo felixdivo merged commit e8c2ee9 into hardbyte:develop Jul 19, 2019
@jsee23 jsee23 deleted the vectorCanFdConfig branch September 13, 2019 07:33
karlding added a commit to karlding/python-can that referenced this pull request Oct 1, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants