From: jrebman@netcom.com (Jim Rebman)
To: blinux-list@redhat.com
Subject: Re: tclx drivers for emacspeak
Date: Thu, 12 Dec 1996 05:44:57 -0800 (PST) [thread overview]
Message-ID: <199612121344.FAA22728@netcom4.netcom.com> (raw)
In-Reply-To: <32AF7722.2DAB@magic.mb.ca> from "Patrick Legg" at Dec 11, 96 09:08:18 pm
> Is there anyplace that has a collection of tclx drivers for emacspeak?
>
> Sure, the programming effort is supposed to be small, but an archive of
> drivers that are even halfway working sounds like a good idea to me.
No, there is no archive of drivers because, there has been no motivation
thus far to develop drivers for anything but the serial DecTalks and the
software DecTalk that runs on the DECAlphas. When developing drivers,
keep in mind that these synthesizers are interfaced through the serial
port (I'm not really sure how the software DECTalk works), because there
are no linux/unix drivers for internal synthesizers. So, if people are
to develop drivers for internal synthesizers they must also develop a
low-level driver for the card, and this will more than likely have to be
at the kernel level. There is one guy who is developing such a low-level
driver for the internal DECTalk, but as he is working on it in his spare
time, he makes no promises as to its release date.
So... great idea, now if somebody with the motivation and the skill
wants to undertake such an effort, I am sure it will be greatly
appreciated by the community at large. Keep in mind that this is the
spirit of linux, and that its success comes from the fact that people
support it because they believe in a alternative to the Microsoft way of
thinking.
-- Jim Rebman <jrebman@netcom.com>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Patrick Legg
` Jim Rebman [this message]
` T. V. Raman
Janina Sajka
Janina Sajka
` Ken Perry
Janina Sajka
` Ken Perry
` Kenneth Albanowski
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=199612121344.FAA22728@netcom4.netcom.com \
--to=jrebman@netcom.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).