From: "Kelly Prescott" <prescott@deltav.org>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Speakup and serial adapter cards
Date: Tue, 24 Jan 2012 22:57:14 -0600 [thread overview]
Message-ID: <000001ccdb1d$ceabc580$6c035080$@org> (raw)
In-Reply-To: <E1RpuIO-0000n4-0f@rings.ka0vba.ampr.org>
I think the problem is actually the way some of the synthesizers do speech
indexing etc.
Because they all do it slightly differently, you would almost have to
abstract it some how.
In principal, the basic i/o access shouldn't be to challenging, but the
underlying command structures and control line adjustment etc for each synth
would probably present some challenges to overcome.
It does, however, seem like a fun and challenging project.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of D. Curtis Willoughby
Sent: Tuesday, January 24, 2012 10:17 PM
To: speakup@braille.uwo.ca
Subject: Re: Speakup and serial adapter cards
Gene and others:
I think we need to separate the problem into two parts, because the two
parts should have different priorities. The first part, and the one with
the highest priority is to make speakup capable of driving any serial port
connected to the system, regardless of whether it is a serial port on the
mother board such as ttyS0, ttyS1, etc., or on a PCI expantion board, or on
a PCI-E board, or on a USB to serial adapter.
The second part of the problem, and the lower priority part is for speakup
to recognize the serial port that is connected to the synthasizer
automatically without human intervention. This is lower priority, because
there are various interventions that could be used to tell speakup which
port to use. Among them, there was once, and maybe still a boot parameter
that can tell speakup which port to use, and it should also be possible to
configure something in initrd to do it.
D. Curtis Willoughby
P.S. I am not quite sure what the actual interface between speakup and the
kernel is, but on the surface it would seem that that interface should be
the same regardless of which port is being used.
If this is true, giving speakup the device filename, or maybe the major and
minor device number should be all that it takes for speakup to drive any
port. The figuring out automatically which port to use may be much harder.
> From speakup-bounces@braille.uwo.ca Tue Jan 24 16:49:56 2012
> Envelope-to: postman@localhost
> Delivery-date: Tue, 24 Jan 2012 16:49:56 -0700
> X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
> new-mail2.hypermall.com
> X-Spam-Level:
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled
> version=3.2.1
> X-Original-To: speakup@braille.uwo.ca
> From: acollins@icsmail.net
> Subject: Re: Speakup and serial adapter cards
> X-Virus-Scanned: Maia Mailguard 1.0.2
> X-BeenThere: speakup@braille.uwo.ca
> X-Mailman-Version: 2.1.14
> List-Id: "Speakup is a screen review system for Linux."
> <speakup.braille.uwo.ca>
> List-Unsubscribe: <http://speech.braille.uwo.ca/mailman/options/speakup>,
> <mailto:speakup-request@braille.uwo.ca?subject=unsubscribe>
> List-Archive: <http://speech.braille.uwo.ca/pipermail/speakup>
> List-Post: <mailto:speakup@braille.uwo.ca>
> List-Help: <mailto:speakup-request@braille.uwo.ca?subject=help>
> List-Subscribe: <http://speech.braille.uwo.ca/mailman/listinfo/speakup>,
> <mailto:speakup-request@braille.uwo.ca?subject=subscribe>
> MIME-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Hello Curt! This is Gene Collins. Part of the problem for Speakup is
> that each of the serial synthesizers are managed by a separate driver.
> They all use the standard irqs and addresses for ttyS0 and ttyS1. I
> think they even support ttys3 and ttys4. Since pci serial ports get
> assigned whatever irq and address is available at boot up, Speakup in
> it's current form has no way to know where to look. I think the same
> situation holds true for usb serial ports. So the question developers
> need to answer is how to poll the system for the existence of any kind
> of serial port, before polling the list of ports for a synth matching
> the driver.
>
> Just a suggestion for a starting place for developers to look at.
>
> Gene Collins
>
> >This is getting to be a big problem!
> >
> >I have a new computer without a serial port. To use a hardware
> >synthasizer like a Doubletalk LT I must use a USB to serial adapter
> >or a PCI-E card. This computer does not have PCI slot(s).
> >If this combination of "cannot do" restrictions is not fixed, serial
> >hardware synthesizers are doomed to become obsolete.
> >
> >I guess there are a few USB synthesizers, and software speach is
> >still well not wonderful. I have not been able to establish whether
> >the few PCI-E cards can manage IRQs and I/O addresses so they are
> >treated like internal serial ports, but I suspect they cannot. Is it
> >not possible to modify speakup so that it can use any serial port on
> >the machine, rather than just ttyS0 and ttyS1? Would you developers
> >please look at a solution for this one? Please!
> >
> >D. Curtis Willoughby
> >
> >> From speakup-bounces@braille.uwo.ca Mon Jan 23 21:57:14 2012
> >> Envelope-to: postman@localhost
> >> Delivery-date: Mon, 23 Jan 2012 21:57:14 -0700
> >> X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
> >> new-mail2.hypermall.com
> >> X-Spam-Level:
> >> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled
> >> version=3.2.1
> >> X-Original-To: speakup@braille.uwo.ca
> >> From: acollins@icsmail.net
> >> Subject: Re: Speakup and serial adapter cards
> >> X-Virus-Scanned: Maia Mailguard 1.0.2
> >> X-BeenThere: speakup@braille.uwo.ca
> >> X-Mailman-Version: 2.1.14
> >> List-Id: "Speakup is a screen review system for Linux."
> >> <speakup.braille.uwo.ca>
> >> List-Unsubscribe:
<http://speech.braille.uwo.ca/mailman/options/speakup>,
> >> <mailto:speakup-request@braille.uwo.ca?subject=unsubscribe>
> >> List-Archive: <http://speech.braille.uwo.ca/pipermail/speakup>
> >> List-Post: <mailto:speakup@braille.uwo.ca>
> >> List-Help: <mailto:speakup-request@braille.uwo.ca?subject=help>
> >> List-Subscribe:
<http://speech.braille.uwo.ca/mailman/listinfo/speakup>,
> >> <mailto:speakup-request@braille.uwo.ca?subject=subscribe>
> >> MIME-Version: 1.0
> >> Content-Type: text/plain; charset="us-ascii"
> >> Content-Transfer-Encoding: 7bit
> >>
> >> Nope, Speakup in now way supports pci serial cards.
> >>
> >> >Hello,
> >> >I know that speakup cannot work with synths connected through a
> >> >USB to seri
> al
> >> adapter, however I would like to confirm whether speakup can use
> >> serial port
> s p
> >> rovided by a PCI-express or PCI serial adapter card? I am most
> >> interested in
> th
> >> e PCI-Express adapter cards.
> >> >
> >> >Michael Whapples
> >> >_______________________________________________
> >> >Speakup mailing list
> >> >Speakup@braille.uwo.ca
> >> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples
` acollins
` D. Curtis Willoughby
` acollins
` D. Curtis Willoughby
` Hart Larry
` Kelly Prescott [this message]
` acollins
` Michael Whapples
` Trevor Astrope
` covici
` John Heim
` John Heim
` Michael Whapples
` John Heim
` Glenn
` John Heim
pj
pj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001ccdb1d$ceabc580$6c035080$@org' \
--to=prescott@deltav.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).