From: Ken Perry <whistler@blinksoft.com>
To: blinux-list@redhat.com
Subject: Re: tclx drivers for emacspeak
Date: Mon, 6 Jan 1997 07:28:12 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.3.95.970106072719.11595A-100000@blinksoft.com> (raw)
In-Reply-To: <199701070222.SAA03836@igc2.igc.apc.org>
Double talk would still need a driver in Linux unless you are talking
about the double talk serial and the lite talk serial.
Ken /whistler
On Mon, 6 Jan 1997, Janina Sajka wrote:
> > Other speech cards that do not communicate to the PC over a serial port but
> > instead talk over the internal bus, e.g. the Dectalk PC, require a
> > device driver that makes the card appear as a serial device to linux.
>
> This is one solid reason why I would prefer a Doubletalk. I don't know
> enough about Linux to know what the Doubletalk would need under Linux,
> but the Doubletalk needs no drivers whatsoever under DOS (and in a DOS
> VDM under OS/2). It is simply addressed as LPT3. End of configuration.
> Simple and tidy. Also much more affordable.
>
> Janina Sajka, Director
> Information Systems Department
> American Foundation for the Blind (AFB)
>
> janina@afb.org
>
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Ken Perry [this message]
-- strict thread matches above, loose matches on Subject: below --
Janina Sajka
` Ken Perry
` Kenneth Albanowski
Janina Sajka
Patrick Legg
` Jim Rebman
` T. V. Raman
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=Pine.LNX.3.95.970106072719.11595A-100000@blinksoft.com \
--to=whistler@blinksoft.com \
--cc=blinux-list@redhat.com \
/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).