| Date | Tue, 08 Sep 2020 12:45:10 -0600 | From | simon@mungewel ... | Subject | Re: [PATCH 4.19 69/88] ALSA: firewire-digi00x: exclude Avid Adrenaline from detection |
| |
On 2020-09-08 09:26, Greg Kroah-Hartman wrote: > From: Takashi Sakamoto <o-takashi@sakamocchi.jp> > > commit acd46a6b6de88569654567810acad2b0a0a25cea upstream. > > Avid Adrenaline is reported that ALSA firewire-digi00x driver is bound > to. > However, as long as he investigated, the design of this model is hardly > similar to the one of Digi 00x family. It's better to exclude the model > from modalias of ALSA firewire-digi00x driver. > > This commit changes device entries so that the model is excluded. >
Just to add my 'ACK-BY'. Yes, the Avid Adrenaline seems to be based around a totally different method of control and will likely need a separate driver.
I believe that this includes the following devices: AVID Adrenaline, AVID Mojo, AVID Mojo SDI, AVID AV Option and others... from Windows driver 'FlameThrower' inf. -- [AvidHardware.NTx86] %Avid_Gryphon% = Flamethrower, 1394\Avid_Technology&Gryphon %Avid_Raven% = Flamethrower, 1394\Avid_Technology&Raven %Avid_Adrenaline% = Flamethrower, 1394\Avid_Technology&Adrenaline %Avid_FireBobPro% = Flamethrower, 1394\Avid_Technology&FireBobPro %Avid_Mojo% = Flamethrower, 1394\Avid_Technology&Mojo %Avid_FireBoB% = Flamethrower, 1394\Avid_Technology&FireBoB %Avid_FireBoBV2% = Flamethrower, 1394\Avid_Technology&FireBoBV2 %Avid_DigiBoB% = Flamethrower, 1394\Avid_Technology&DigiBoB %Avid_AVoptionV10% = Flamethrower, 1394\Avid_Technology&AVoptionV10 --
There are some details in this thread, for anyone interested in following up. https://sourceforge.net/p/ffado/mailman/message/37078754/
Cheers, Simon.
PS. Have a Mojo SDI inbound, will confirm when it arrives.
|