alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "S. Christian Collins" <s.chriscollins@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, Mark Hills <mark@xwax.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: "alsactl store" fails to save Echo Gina3G mixer
Date: Tue, 3 Oct 2017 13:05:48 -0500	[thread overview]
Message-ID: <30aadbb2-7e27-06f5-2bf6-6e0eb1527423@gmail.com> (raw)
In-Reply-To: <5a3cbe62-f0c6-17eb-7e5b-5ece7964546c@sakamocchi.jp>

I will be happy to help you test, when that time comes.

Best Regards,

-~Chris


On 10/02/2017 08:53 PM, Takashi Sakamoto wrote:
> 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.html 
>
>
> 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.html
> [2] 
> http://mailman.alsa-project.org/pipermail/alsa-devel/2017-October/126033.html
>
>
> Takashi Sakamoto

  reply	other threads:[~2017-10-03 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 15:34 "alsactl store" fails to save Echo Gina3G mixer S. Christian Collins
2017-08-29  3:33 ` Takashi Sakamoto
2017-08-29  3:46   ` S. Christian Collins
2017-08-31  3:50     ` Takashi Sakamoto
2017-08-31 20:25       ` S. Christian Collins
2017-09-04 20:23       ` Mark Hills
2017-09-14 13:40         ` S. Christian Collins
2017-09-15  5:21           ` Takashi Sakamoto
2017-10-03  1:53             ` Takashi Sakamoto
2017-10-03 18:05               ` S. Christian Collins [this message]
2017-08-29 20:36   ` Mark Hills
2017-08-30 14:17     ` S. Christian Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30aadbb2-7e27-06f5-2bf6-6e0eb1527423@gmail.com \
    --to=s.chriscollins@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=mark@xwax.org \
    --cc=o-takashi@sakamocchi.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).