MT76 Driver Support for ra* device instances. #15
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adding Support to the Belabox UI for the MT76 Driver, used in the Linksys AE6000.
This Driver DKMS is pretty stable on Ubuntu 18.04 on the Jetson Nano, and allows for multiple instances of the same card to be on the device. I've switched over to using these usb dongles instead of the more popular
rtlbased ones.The problem is: It uses a different Network Device id:
ra*To get around this, I simply added a separate match in
belaUI.jsforra, which does allow it to be controlled viabelaUI.I'd like to also know where I can push code to add the dkms to the image build and the updates to the network manager to control it.