Added support for HDSPe MADI FX with new (?) vendor id #6
+10
−1
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
|
We also had the problem that one of our customers bought a new MadiFX card and this was not detected anymore. With this patch the card is now detected and working again. |
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.
Hello,
This PR adds support for the HDSPe MADI FX Triple MADI Card (or maybe just the specific card we have?).
The Card in our possession uses a different PCI vendor id then the one used in this driver.
The vendor id in question (
0x1d18) is not defined in thepci_ids.h(linux kernel 6.1.80), so i have defined it in the filemadifx.c.I did some minimal testing (checking that audio comes out and in on some channels by connecting an input of the card to an output)
In a couple of days i will be able to find out if more MADI FX Cards use this new vendor id.
Kind Regards