From: Gregory Nowak <greg@gregn.net>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: speakup: refactor synths array to use a list
Date: Sun, 17 Jun 2018 22:34:44 -0700 [thread overview]
Message-ID: <20180618053444.GA1614@gregn.net> (raw)
In-Reply-To: <20180612063105.7urgjfckrwjvqs6k@var.youpi.perso.aquilenet.fr>
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. Doing rmmod of all three speakup modules comes back with
no errors. There is also no unusual output in dmesg, I can see both
synthesizers being registered and unregistered as I switch between
them.
I can also reproduce this behavior with speakup_soft, and speakup_dummy
specifically:
1. modprobe speakup_soft and modprobe speakup_dummy
2. The synthesizer should now be set to dummy in
/sys/accessibility/speakup/synth.
3. Use the speakup review keys, press enter a number of times. You
should observe output from both the software speech, and from the
serial port alternating between each other.
4. echo soft >/sys/accessibility/speakup/synth
5. You should observe no output from either software speech or the
serial port as you use speakup review keys, or press enter
repeatedly.
6. echo dummy >/sys/accessibility/speakup/synth
7. You should alternately get speech from the software synthesizer and
from the serial port.
I built my kernel from the 4.17.1 kernel.org sources, and the patch
that Samuel reposted applied cleanly with no errors.
Greg
--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.
--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
next prev parent reply other threads:[~2018-06-18 5:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 9:52 [PATCH] staging: speakup: refactor synths array to use a list Justin Skists
2018-06-04 9:57 ` Samuel Thibault
2018-06-06 13:26 ` Samuel Thibault
2018-06-06 20:28 ` Justin Skists
2018-06-11 22:57 ` Samuel Thibault
2018-06-11 23:51 ` Gregory Nowak
2018-06-12 6:31 ` Samuel Thibault
2018-06-18 5:34 ` Gregory Nowak [this message]
2018-06-18 6:22 ` Samuel Thibault
2018-06-18 8:41 ` Justin Skists
2018-06-18 8:46 ` Samuel Thibault
2018-06-18 8:55 ` Justin Skists
2018-06-18 8:58 ` Samuel Thibault
2018-06-11 23:55 ` John Covici
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=20180618053444.GA1614@gregn.net \
--to=greg@gregn.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.