[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1117674358.626563.1529311304239@email.1and1.co.uk>
Date: Mon, 18 Jun 2018 09:41:44 +0100 (BST)
From: Justin Skists <justin.skists@...za.co.uk>
To: devel@...verdev.osuosl.org, gregkh@...uxfoundation.org,
Samuel Thibault <samuel.thibault@...-lyon.org>,
"Speakup is a screen review system for Linux."
<speakup@...ux-speakup.org>, Gregory Nowak <greg@...gn.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: speakup: refactor synths array to use a list
> On 18 June 2018 at 06:34 Gregory Nowak <greg@...gn.net> wrote:
>
>
> On Tue, Jun 12, 2018 at 08:31:06AM +0200, Samuel Thibault wrote:
> > The load/unload is about the module itself, i.e. modprobe speakup_bns ;
> > modprobe speakup_soft, switch between them, then rmmod speakup_bns ;
> > speakup_soft or the converse (to exercise both orders).
>
> # uname -a
> Linux p41box 4.17.1 #1 SMP Sat Jun 16 11:19:57 MST 2018 i686 GNU/Linux
> # lsmod |grep "speakup"
> speakup_bns 16384 0
> speakup_soft 16384 1
> speakup 94208 3 speakup_bns,speakup_soft
>
> With /sys/accessibility/speakup/synth set to bns, I am getting output
> alternately from the bns and from soft. It's as if speakup can't make
> up its mind which synthesizer is being used. When I echo soft
> >/sys/accessibility/speakup/synth, I get no speech at all from either
> synthesizer.
Is this a known issue, or a regression due to the patch?
Justin.
Powered by blists - more mailing lists