From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Dec Talk internal cards supported?
Date: Tue, 1 Oct 2002 19:57:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210011947120.1314-100000@igueths> (raw)
In-Reply-To: <024901c2699b$ef94d0f0$6701a8c0@6S4X011>
Hi. I was going to modularize the dectalk driver, but unfortunately
couldn't due to time constraints. I am currently working on patching
Unreal Ircd, so it is on my todo list. Kirk, why didn't you modularize the
speakup mods from the start? Bc now having to do it vs could have done it
a while ago can save you time. I think that Speakup is a great product,
both from a code and user perspective. Do you intend to add modprobe
functionality to the various mods? Bc what you could do is stack the
Speakup esential module ontop of all the synth modules. So if I did
modprobe speakup_dectlk it would load speakup_dectlk.o, speakup.o, and all
other necessary dependencies. Just a thought.
microsoft dialogue
This company has performed an illegal operation and will be shut down.
If the problem persists, delete winblows and install linux
close button
On Tue, 1 Oct 2002, Erik Heil wrote:
> Hi there. How would one download the necissary software onto the Dectalk
> board? BC what I was thinking is possibly modify the firmware on the board
> so that it doesn't need to be downloaded or sent an init command.
> ----- Original Message -----
> From: "Gene Collins" <collins@gene3.ait.iastate.edu>
> To: <speakup@braille.uwo.ca>
> Sent: Tuesday, October 01, 2002 2:33 PM
> Subject: Re: Dec Talk internal cards supported?
>
>
> > Hello all. There are no dectalk internal boards supported to my
> > knowledge. Only the external serial dectalk express and the original
> > dectalk external synthesizers are supported. The problem with the
> > internal isa cards is that they have to have software downloaded onto
> > the card before they can be used. Since Speakup is activated and
> > initialized almost the first thing after the kernel is loaded and
> > initialized, and before the file system is available, there is at
> > present no way to have the kernel download the software onto the
> > internal dectalk boards. I believe you can use these boards with emacs
> > speak, but I am not familiar with it, and so can not say. Making these
> > dectalk boards usable is on Kirk's to do list, but there are a number of
> > things that have to happen first, such as the almost complete rewrite of
> > Speakup to make it usable with the 2.2.5 kernels, and the modularization
> > of the synthesizer drivers, before a dectalk-pc driver could be written.
> >
> > Gene
> >
> > >It is difficult to find computers or have on ebuilt with the isa slots
> > >required for the dec pc's. So $150 might be unrealistic.
> > >
> > >-- charlie.
> >
> > _______________________________________________
> > 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: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
Bear in SFO
` Adam Myrow
[not found] ` <Pine.LNX.4.44.0209291559450.3936-100000@homerun.midsouth.r r.com>
` Bear in SFO
` ccrawford
[not found] ` <Pine.LNX.4.44.0209300823550.27961-100000@localhost.localdo main>
` Bear in SFO
` Charles Crawford
` Gene Collins
` Erik Heil
` Patrick Turnage
` Jude DaShiell
` Geoff Shang
` Erik Heil
` Adam Myrow
` Geoff Shang
` shaun_oliver
` Igor Gueths [this message]
` Geoff Shang
` Bear in SFO
` Bear in SFO
` Where do I get Redhat 8? ccrawford
` Janina Sajka
` Edward L. Barnes
[not found] ` <Pine.LNX.4.44.0210020522580.8234-100000@localhost.localdom ain>
` Bear in SFO
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.4.44.0210011947120.1314-100000@igueths \
--to=igueths@attbi.com \
--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).