Thanks to everyone for all the input so far. I didn't realize that some of the modules with the .conf files also have binaries as the backend. I do indeed see that they're there in /usr/lib/speech-dispatcher on my system. I'll have to look at the speech-dispatcher code, and see how they do what they do. I'm still in favor of letting speakup drive the serial synth. Thanks to Samuel's comment below, I know what part of the speakup code to look at, and the comment that it should be a fairly simple beginner kernel hacking project is encouraging. I'll add this project to my to do list, and will explore it once I have more time, hopefully sooner rather than later. Thanks again. Greg On Fri, Feb 07, 2020 at 09:10:24AM +0100, Samuel Thibault wrote: > Indeed. But there is another approach, which was made for this: using > /dev/synth. For now that file only supports writing to it to get > text emitted, but ioctls can be defined to drive it, such as setting > pitch etc. in a portable way across synthesizers (speakup will handle > these details), but also interrupting. That all happens in speakup's > devsynth.c and can be a relatively easy task for kernel hacking > beginners. > > Samuel > _______________________________________________ > Speakup mailing list > Speakup@xxxxxxxxxxxxxxxxx > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- 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@xxxxxx _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
