From: Jacob Schmude <jacobs@ncinter.net>
To: speakup@braille.uwo.ca
Subject: Re: bug in 0.09a
Date: Mon, 19 Jun 2000 23:59:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0006192336480.1213-100000@jscp> (raw)
In-Reply-To: <Pine.GSO.4.21.0006192301090.142-200000@funky.ultrashell.net>
Hi
I believe this was the bug that it was supposed to fix. If you
know how to program in C, edit speakup_dtlk.c and change synth_portlist[]
to only include your port, and the ending 0. If you aren't a C programmer,
forget I said it. For some reason, kernel 2.4.0-test1 has a device probing
problem and this is what I did to get my internal doubletalk to work after
Kirk told us on the list that's what we had to do. I'm not a very good
programmer myself but I'm learning.
On Mon, 19 Jun 2000, Ryan M. wrote:
> Hi. I tried Speakup version 0.09a with Linux version 2.4.0-test1 and an
> internal doubletalk, and Speakup didn't find my internal doubletalk. My
> internal Doubletalk works with Speakup 0.09 and Linux version 2.2.16, so
> I'm guessing it is a bug in Speakup 0.09a. I attached my kernel messages
> from when I booted 2.4.0-test1 to this message. Thanks.
>
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Ryan M.
` Jacob Schmude [this message]
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.21.0006192336480.1213-100000@jscp \
--to=jacobs@ncinter.net \
--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).