You can treat the serial port like a file (this is linux after all),
just do open in the i nit section and write characters to the file.
The name will be something like /dev/ttyS0 or similar. Note the
capital S. As an example look at the espeak driver, so you get all
the things in the right places.
On Thu, 06 Feb 2020 23:29:43 -0500,
Gregory Nowak wrote:
>
> Right, this would require a speech-dispatcher module file. The thing
> I'm not sure about is how to do the serial port I/O from
> speech-dispatcher. The speech-dispatcher modules are .conf files, so
> maybe the answer would be a separate program to expose the serial port
> to speech-dispatcher modules, or a modification to the actual
> speech-dispatcher code to do that.
>
> What I like about the synth_direct approach is that speakup already
> does the heavy lifting, and speakup and gnome-speech would use
> speakup's interface to talk to the synth, which would mean they both
> wouldn't be setting parameters and causing a mess. The disadvantage is
> it requires speakup to be loaded, which I already use anyway, so it
> doesn't bother me personally.
>
> Greg
>
>
> On Thu, Feb 06, 2020 at 11:10:24PM -0500, John Covici wrote:
> > You might need to write a driver in speech-dispatcher, that would do
> > exactly what you want. I have been thinking about this for years, but
> > never had the time to do it.
>
>
> --
> 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
>
