Hi S. Christian and Mark,
On Sep 15 2017 14:21, Takashi Sakamoto wrote:
On Sep 14 2017 22:40, S. Christian Collins wrote:
Takashi, is there anything else you would like me to do to help with this issue? Should it perhaps be filed on the bug tracker so it doesn't get lost in this list?
Sorry to be late for reaction, but we're on merge window for v4.14 and I keep my time for unexpected accidents such as this[1]. I'd like to postpone this discussion after closing the window, a few days later.
[1] http://mailman.alsa-project.org/pipermail/alsa-devel/2017-September/125474.h...
First of all, I apologize for the inconvenience. It's my fault. Yesterday a maintainer of this subsystem applies my patch[1] to revert the issued commit. It will also be applied to stable/longterm kernels. If you use one of the maintained kernels in any distribution such as Fedora, you may get solved driver enough later.
However, current echoaudio drivers have an issue in a point of ALSA control interface, as I noted to the patch. For this issue, I'm preparing for my proposal in Audio miniconference 2017[2]. If the 'echomixer' program is going to be modified according to our decision, I'll request you to test my patches, perhaps. I'm happy to get your helps for the testing in future.
Thanks for your report for this issue, and patience.
[1] http://mailman.alsa-project.org/pipermail/alsa-devel/2017-October/126030.htm... [2] http://mailman.alsa-project.org/pipermail/alsa-devel/2017-October/126033.htm...
Takashi Sakamoto