* need comments
@ Kirk Reiser
` Whistler
` Christopher Moore
0 siblings, 2 replies; 8+ messages in thread
From: Kirk Reiser @ UTC (permalink / raw)
To: speakup
Hi again folks: The current way that I do probing for synths is
reliable sometimes and with some synths. I have been trying to decide
how I could make it more reliable more often. The reason we have
these probing problems is because many of the synths are not designed
to interact with the system controlling them. They are designed to
take data and commands and just execute them. What I have been toying
with doing is just cycle through the ports checking to see if I have
CTS and if so, saying okay, I got it.
My question to you all is do you think this is an acceptable way of
going about it? It would mean that a person with a serial synth would
need to have it on the lowest serial port to have it found reliably.
I would be interested in your opinions. If you don't like the idea,
then I would like a workable suggestion for how to make it work. I am
not interested in criticism without an alternative solution.
Kirk
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: need comments
need comments Kirk Reiser
@ ` Whistler
` Kirk Reiser
` cpt.kirk
` Christopher Moore
1 sibling, 2 replies; 8+ messages in thread
From: Whistler @ UTC (permalink / raw)
To: speakup
I like this as long as we know we could adjust our speech till we get
things working I mean if we realy must have something on our lower serial
ports we can put it on later after all the set up is done.
Of corse you could run the check for those sound cards that do reply first
and then if that don't work grab the first serial device and say your
mine.
ken
On Tue, 28 Mar 2000, Kirk Reiser wrote:
> Hi again folks: The current way that I do probing for synths is
> reliable sometimes and with some synths. I have been trying to decide
> how I could make it more reliable more often. The reason we have
> these probing problems is because many of the synths are not designed
> to interact with the system controlling them. They are designed to
> take data and commands and just execute them. What I have been toying
> with doing is just cycle through the ports checking to see if I have
> CTS and if so, saying okay, I got it.
>
> My question to you all is do you think this is an acceptable way of
> going about it? It would mean that a person with a serial synth would
> need to have it on the lowest serial port to have it found reliably.
> I would be interested in your opinions. If you don't like the idea,
> then I would like a workable suggestion for how to make it work. I am
> not interested in criticism without an alternative solution.
>
> Kirk
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: need comments
need comments Kirk Reiser
` Whistler
@ ` Christopher Moore
` Kirk Reiser
1 sibling, 1 reply; 8+ messages in thread
From: Christopher Moore @ UTC (permalink / raw)
To: speakup
Kirk,
On my machine, I have a Braille device on /dev/ttyS0 which would confuse
your scheme of looking for the first cts.
Is there a way to pass the synthesizer/port info to the kernel? If so,
this approach would simplify things from the user's perspective. Now, if
you want to changes synthesizers, you need to recompile your kernel. If
parms could be passed to the kernel, this would be unnecessary.
Chris
w1gm@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: need comments
` Christopher Moore
@ ` Kirk Reiser
0 siblings, 0 replies; 8+ messages in thread
From: Kirk Reiser @ UTC (permalink / raw)
To: speakup
Christopher Moore <w1gm@sdf.lonestar.org> writes:
> On my machine, I have a Braille device on /dev/ttyS0 which would confuse
> your scheme of looking for the first cts.
> Is there a way to pass the synthesizer/port info to the kernel? If so,
I think I mentioned that in my original or a subsequent message. Even
currently you can tell speakup where your synth is with the
speakup_ser=n option on the kernel command line. N is any number
between 0 and three depending on how many serial ports you have
installed.
> this approach would simplify things from the user's perspective. Now, if
> you want to changes synthesizers, you need to recompile your kernel. If
> parms could be passed to the kernel, this would be unnecessary.
I wish it were this simple. But! if you're volunteering to help... No problem!
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
need comments Kirk Reiser
` Whistler
` Kirk Reiser
` Whistler
` cpt.kirk
` Buddy Brannan
` Christopher Moore
` Kirk Reiser
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).