* yasr on /dev/ttyS1: is that a problem?
@ Cheryl Homiak
` Mike Gorse
0 siblings, 1 reply; 3+ messages in thread
From: Cheryl Homiak @ UTC (permalink / raw)
To: blinux-list
Yasr is working very nicely on the serial port of my laptop with a doubletalk
lt. However, when i decided to try this on my desktop, I ran into problems. My
braillelite is on /dev/ttyS0 so I instructed yasr to use /dev/ttyS1. I never got
any sound from yasr and my braillelite locked up partially, giving some output
when I arrowed up or down but the advance bar failing to respond at all. I can
easily use speakup and brltty together, so this isn't a really big issue, but it
did make me wonder. does yasr have problems with /dev/ttyS1 or does it have
problems with equipment running on other serial ports when it is running or what
would be the cause of my problem? The syntax I used was
yasr -s DoubleTalk -p /dev/ttyS1
this is the same syntax I used on my laptop, with the exception of the different
serial port.
Thanks for any input.
Cheryl
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: yasr on /dev/ttyS1: is that a problem?
yasr on /dev/ttyS1: is that a problem? Cheryl Homiak
@ ` Mike Gorse
` Cheryl Homiak
0 siblings, 1 reply; 3+ messages in thread
From: Mike Gorse @ UTC (permalink / raw)
To: blinux-list
Cheryl,
It is a bug in yasr. Below is a patch.
--
--- yasr/main.c.orig 2003-05-14 23:09:22.000000000 -0400
+++ yasr/main.c 2003-05-21 22:59:34.000000000 -0400
@@ -1226,10 +1226,12 @@
case 's':
(void) sprintf((char *) buf, "synthesizer=%s", optarg);
opt_read((char *) buf, 0);
+ cl_synth = 1;
break;
case 'p':
(void) sprintf((char *) buf, "synthesizer port=%s", optarg);
opt_read((char *) buf, 0);
+ cl_synthport = 1;
break;
default:
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
yasr on /dev/ttyS1: is that a problem? Cheryl Homiak
` Mike Gorse
` Cheryl Homiak
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).