speakup from git question

Gregory Nowak greg at romuald.net.eu.org
Sun Oct 14 21:15:57 EDT 2007

Hash: SHA1

Hi all.

I have a very simple question. I know I could find the answer out
myself by trial and error, but I thought I'd ask here, so as to save
myself from having to rebuild my kernel multiple times.

What I'd like to know is simply if I understand the following
correctly, or not. If you build speakup as modules, you can switch
from synth to synth, but you lose the ability to have speakup come up
as soon as possible, before the file systems get mounted, (this
assumes you aren't using an initrd). If you build
spkglue, and speakup into the kernel, you'll get speech as soon as
possible, and you can still switch to another synth by loading its
module later on, but the only way to switch back to a built-in synth
as of now is to reboot the machine. Do I have this right, and if so,
am I correct also in assuming that this gives more weight to the
argument for using an initrd, as opposed to not using one?

Also, since /proc/speakup/synth_name, or an equivalent doesn't exist
as of now, is the best way to check if a synth is already loaded or
not in a script by doing a grep against lsmod, or is there a better

Finally, does the version of speakup currently in git support usb to
serial converters, and other nonstandard ports, or is that still to
come? I'm pretty sure the answer is no, but I thought I'd ask
anyway. As always, thanks in advance.


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager at EU.org
Version: GnuPG v1.4.6 (GNU/Linux)


More information about the Speakup mailing list