Prevent mixing can interfaces (wrong) numbering when usb to can inter… #24
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
…faces are installed.
jhofstee
force-pushed
the
master
branch
2 times, most recently
from
7a10483 to
17fc93b
Compare
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.
Currently, udev rule maps can0 based on the kernel interface name. But when you connect an usb to can adapter sometimes this interface gets can0. In this case the real can0 interface will not used and appears as can2. This will break the configuration because VE.can devices are now on can0.
Change the udev rule maps strict the device 1c2bc00.can to can0 and prevents that issue.