On Mar 20 2015 23:13, Takashi Iwai wrote:
At Fri, 20 Mar 2015 22:51:25 +0900, Takashi Sakamoto wrote:
On Mar 20 2015 22:35, Takashi Iwai wrote:
I don't think it possible to argue the other ALSA developers for going to include such vendor-specific or model-specific huge codes to alsa-lib... (Except for intel HDA)
Why not implementing as a plugin?
As long as I know, we cannot write any configuration to load it for 'hw' node. On the other hand, when adding any nodes like 'bebob' or 'dice', they always stay in alsa-lib configuration space even if there're no actual devices connected.
If my understanding is wrong, please inform it to me.
You seem mixing up how to use the plugin setup and how to write the plugin... The usage with a plugin might be more complex indeed, but it's more or less same no matter whether you implement in alsa-lib itself or implement as an external plugin.
Sorry, but I consider about one-step future.
I think it possible to discuss constructively about such plugins for alsa-plugins, while its usage is not so easy for usual users of FireWire audio devices. I can imagine to receive much requests about improvements, then consider about including it to alsa-lib itself. But this idea may be hard to achieve because of the reasons I describe.
I felt a bit unhappiness about your question and had a logic jump, sorry. I'm not so tough developer...
Regards
Takashi Sakamoto