* Speakup options @ Michael Whapples ` Samuel Thibault 0 siblings, 1 reply; 9+ messages in thread From: Michael Whapples @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Hello, Is it possible to specify some of the speakup options when loading speakup modules? An example of this is can I load the speakup_apollo module specifying the serial port like I can when using speakup built in to the kernel with the speakup.ser=x option at the boot prompt? Also how about the speakup.quiet option, can that be specified? The reason I am asking is that GRML now has speakup as modules but the speakup.synth=synth_name option from the boot prompt is being supported by scripts in the grml-autoconfig package and I feel it would be good if it could support all the speakup boot options. Michael Whapples ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Speakup options Speakup options Michael Whapples @ ` Samuel Thibault ` Michael Whapples 0 siblings, 1 reply; 9+ messages in thread From: Samuel Thibault @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Michael Whapples, le Wed 08 Apr 2009 13:41:56 +0000, a écrit : > Is it possible to specify some of the speakup options when loading > speakup modules? Yes, just like other options, throw lines in a file in /etc/modprobe.d, like: options speakup_apollo ser=x Samuel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Speakup options ` Samuel Thibault @ ` Michael Whapples ` Samuel Thibault ` Kerry Hoath 0 siblings, 2 replies; 9+ messages in thread From: Michael Whapples @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Thanks. I have just been having a bit of a play with it now with the modprobe command, it seems like some of the options belong to the synth modules and some to the speakup core module, eg. ser should go with speakup_apollo but not with speakup module and quiet seems it should go with speakup module but not speakup_apollo. Is there a document somewhere stating which option belongs with which module? Michael Whapples On 23/12/42 19:59, Samuel Thibault wrote: > Michael Whapples, le Wed 08 Apr 2009 13:41:56 +0000, a écrit : > >> Is it possible to specify some of the speakup options when loading >> speakup modules? >> > Yes, just like other options, throw lines in a file in /etc/modprobe.d, > like: > > options speakup_apollo ser= > Samuel > > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Speakup options ` Michael Whapples @ ` Samuel Thibault ` Michael Prokop ` Kerry Hoath 1 sibling, 1 reply; 9+ messages in thread From: Samuel Thibault @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Michael Whapples, le Wed 08 Apr 2009 16:23:59 +0000, a écrit : > Is there a document somewhere stating which option belongs with which > module? Better than a document, a command: modinfo speakup Samuel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Speakup options ` Samuel Thibault @ ` Michael Prokop ` Gregory Nowak 0 siblings, 1 reply; 9+ messages in thread From: Michael Prokop @ UTC (permalink / raw) To: speakup * Samuel Thibault <samuel.thibault@ens-lyon.org> wrote: > Michael Whapples, le Wed 08 Apr 2009 16:23:59 +0000, a écrit : >> Is there a document somewhere stating which option belongs with which >> module? > Better than a document, a command: modinfo speakup Looking at the options of all the speakup modules in kernel version 2.6.28, the unified part of them is: parm: port:Set the port for the synthesizer (override probing). (int) parm: quiet:Do not announce when the synthesizer is found. (bool) parm: ser:Set the serial port for the synthesizer (0-based). (int) parm: start:Start the synthesizer once it is loaded. (short) parm: synth:Synth to start if speakup is built in. (charp) speakup.synth=.... should work with the next grml release as I've added support for loading the according module to grml. For example specifying speakup.synth=dectlk as bootoption will load the module speakup_dectlk then. My question is: do I have to take care of port/quiet/ser/start as well on my own? If so: what's the most elegant way to support that? (Sorry, I don't have the according hardware on my own, so my test scenario involves just the software speakup part of it.) Thanks to Michael Whapples for his feedback in grml's bug tracking system and to Samuel Thibault for his great work on the speakup source modules within Debian. -mika- -- ,'"`. http://michael-prokop.at/ ( grml.org -» Linux Live-CD for texttool-users and sysadmins `._,' http://grml.org/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Speakup options ` Michael Prokop @ ` Gregory Nowak ` Michael Prokop 0 siblings, 1 reply; 9+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Apr 09, 2009 at 12:58:25AM +0200, Michael Prokop wrote: > My question is: do I have to take care of port/quiet/ser/start as > well on my own? If so: what's the most elegant way to support that? You'll need to provide the ability for relevant parameters to be passed to appropriate modules, if the user supplies them at boot. You may want to look at the syntax we use in systemrescuecd to do this: http://www.sysresccd.org/Speakup-info#Booting_with_Speakup_in_SystemRescueCD_1.1.0_and_later and the section after that one might be of use as well. The way we do this is to look at /proc/cmdline, and start parsing out the options, starting with "speakup=". If the quite option is passed, we invoke speakup_main with quiet=1. For "synth=", we just invoke that particular module, (I.E. synth=bns invokes speakup_bns, synth=dtlk, invokes speakup_dtlk, and so on). As for the other options, we simply pass them to the particular synthesizer module, expecting that the user will know which options a particular synth module takes, (I.E. that speakup_bns takes ser=, but that speakup_dtlk takes port=). Hth. Greg - -- 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@EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkndQnwACgkQ7s9z/XlyUyDvrgCgimo8g3JP7xIzdWbpHpRCH1C7 Ch8An283AVPvHzHmKeaKOYTO0H4uXRB3 =EciJ -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Speakup options ` Gregory Nowak @ ` Michael Prokop ` Gregory Nowak 0 siblings, 1 reply; 9+ messages in thread From: Michael Prokop @ UTC (permalink / raw) To: speakup * Gregory Nowak <greg@romuald.net.eu.org> wrote: > On Thu, Apr 09, 2009 at 12:58:25AM +0200, Michael Prokop wrote: >> My question is: do I have to take care of port/quiet/ser/start as >> well on my own? If so: what's the most elegant way to support that? > You'll need to provide the ability for relevant parameters to be > passed to appropriate modules, if the user supplies them at boot. You > may want to look at the syntax we use in systemrescuecd to do this: > http://www.sysresccd.org/Speakup-info#Booting_with_Speakup_in_SystemRescueCD_1.1.0_and_later > and the section after that one might be of use as well. The way we do > this is to look at /proc/cmdline, and start parsing out the options, > starting with "speakup=". If the quite option is passed, we invoke > speakup_main with quiet=1. For "synth=", we just invoke that > particular module, (I.E. synth=bns invokes speakup_bns, synth=dtlk, > invokes speakup_dtlk, and so on). As for the other options, we simply > pass them to the particular synthesizer module, expecting that the > user will know which options a particular synth module takes, > (I.E. that speakup_bns takes ser=, but that speakup_dtlk takes > port=). Hth. I was hoping to get around the /proc/cmdline parsing, but I think I'll use the same approach as in systemrescuecd. Thanks! regards, -mika- -- ,'"`. http://michael-prokop.at/ ( grml.org -» Linux Live-CD for texttool-users and sysadmins `._,' http://grml.org/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Speakup options ` Michael Prokop @ ` Gregory Nowak 0 siblings, 0 replies; 9+ messages in thread From: Gregory Nowak @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Apr 10, 2009 at 01:53:29AM +0200, Michael Prokop wrote: > I was hoping to get around the /proc/cmdline parsing, but I > think I'll use the same approach as in systemrescuecd. Thanks! /proc/cmdline parsing was the natural way to go in SystemRescueCD, because we're parsing that already anyway. However, I've been sitting here for a few minutes after reading your post, trying to think of a way to do this without /proc/cmdline parsing, and I really don't see any other way, except for parsing dmesg output, which is more difficult, and more prone to error I think. Greg - -- 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@EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknekgoACgkQ7s9z/XlyUyBJ3ACcClCwPmIFLtU7eSvili0OqPbb +J8An0yn15freEinsdntAMef4ktTC15d =a13M -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Re: Speakup options ` Michael Whapples ` Samuel Thibault @ ` Kerry Hoath 1 sibling, 0 replies; 9+ messages in thread From: Kerry Hoath @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. modinfo modulename That is the best way Regards, Kerry. ----- Original Message ----- From: "Michael Whapples" <mwhapples@aim.com> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca> Sent: Thursday, April 09, 2009 12:23 AM Subject: Re: Re: Speakup options Thanks. I have just been having a bit of a play with it now with the modprobe command, it seems like some of the options belong to the synth modules and some to the speakup core module, eg. ser should go with speakup_apollo but not with speakup module and quiet seems it should go with speakup module but not speakup_apollo. Is there a document somewhere stating which option belongs with which module? Michael Whapples On 23/12/42 19:59, Samuel Thibault wrote: > Michael Whapples, le Wed 08 Apr 2009 13:41:56 +0000, a écrit : > >> Is it possible to specify some of the speakup options when loading >> speakup modules? >> > Yes, just like other options, throw lines in a file in /etc/modprobe.d, > like: > > options speakup_apollo ser= > Samuel > > _______________________________________________ Speakup mailing list Speakup@braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Speakup options Michael Whapples
` Samuel Thibault
` Michael Whapples
` Samuel Thibault
` Michael Prokop
` Gregory Nowak
` Michael Prokop
` Gregory Nowak
` Kerry Hoath
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).