Le 01/05/2020 à 14:51, Alexandre Ratchov a écrit :
On Fri, May 01, 2020 at 01:34:54PM +0200, Damien Couderc wrote:
Hi,
I noticed that audioctl and mixerctl both use /dev/audioctl0 as a default
since the reimplementation of the new api.
Shouldn't it use the /dev/audioctl link instead to permit
Alexandre Ratchov wrote:
> On Fri, May 01, 2020 at 01:34:54PM +0200, Damien Couderc wrote:
> > Hi,
> >
> > I noticed that audioctl and mixerctl both use /dev/audioctl0 as a default
> > since the reimplementation of the new api.
> >
> > Shouldn't it use the /dev/audioctl link instead to permit c
On Fri, May 01, 2020 at 01:34:54PM +0200, Damien Couderc wrote:
> Hi,
>
> I noticed that audioctl and mixerctl both use /dev/audioctl0 as a default
> since the reimplementation of the new api.
>
> Shouldn't it use the /dev/audioctl link instead to permit choosing which
> device we want as the def
Hi,
I noticed that audioctl and mixerctl both use /dev/audioctl0 as a
default since the reimplementation of the new api.
Shouldn't it use the /dev/audioctl link instead to permit choosing which
device we want as the default?
--- audioctl.c.orig Fri May 1 13:29:01 2020
+++ audioctl.c
