[issue661] Support speakup boot options in grml-autoconfig

[Michael Whapples]

New submission from Michael Whapples <mwhapples at aim.com>:

It would be nice to see support for some of the extra boot options for speakup
in grml-autoconfig. Currently grml-autoconfig supports the
speakup.synth=synth_name option but none of the others. The main ones I feel
should be supported are speakup.ser=x (x represents a value for the serial port
number) which tells speakup which serial port a hardware synthesiser is
connected to, and the speakup.quiet=x option (x being 0 for off (same as not
specifying) or 1 for on/true) which makes speakup silent by default until a key
is pressed (useful for stopping speakup speaking all the boot messages if you
happen to leave the computer while it boots).

These options do seem poorly documented but the slackware docs for speakup
(ftp.slackware.at/slackware-current/source/k/README_SPEAKUP_PATCH.TXT) explains
this. That slackware doc also mentions speakup.port but I am unsure what that does.

I don't know whether this can be given to speakup when loading modules, but I
think if the core part of speakup is loaded first (the module named speakup)
before we try and load the synthesiser speakup modules (eg. speakup_apollo,
speakup_soft, etc) then we can configure this in the speakup sys area (eg.
/sys/modules/speakup/parameters/ (assuming speakup entirely as modules as
currently done in grml)) by echoing to the appropriate file.

I have just had a quick look now on my system and it appears that speakup.quiet
can be given to speakup module as the quiet option and the speakup.ser option
can be given to the synth modules (on my system I use speakup_apollo) as the ser
parameter. So the commands I give for the same as "speakup.synth=apollo
speakup.ser=0 speakup.quiet=1" would be:
modprobe speakup quiet=1
modprobe speakup_apollo ser=0

----------
messages: 2168
nosy: mwhapples
priority: wish
status: unread
title: Support speakup boot options in grml-autoconfig

_____________________________________
GRML issue tracker <bts at bts.grml.org>
<http://bts.grml.org/grml/issue661>
_____________________________________