From: "Robert Spangler" <spangler.robert@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Issues with latest Speakup on 2.6.25.4
Date: Tue, 3 Jun 2008 14:03:54 -0400 [thread overview]
Message-ID: <AEE30F68FCE5431A9DA5871E3160B045@dictat0r> (raw)
Hello all,
I retrieved the latest Speakup source from Git and patched it into the
kernel. I copied my old .config file from my 2.6.25 source tree to the
2.6.25.4 tree, compiled and installed the new kernel. Now when I boot,
Speakup comes up talking but I am unable to silence it with the enter key on
the keypad. I decided to let it talk it's way through the entire boot
process. It stops speaking at some point, I think before the loading of
init. Now, the keyboard and everything works because I am able to log in.
I can confirm this by logging in and pressing backspace to hear the prompt
beep. Are some things broken in the Git code due to moving from a linear
buffer to a circular one? I am using a DoubleTalk LT if that makes a
difference.
Thanks,
Robby
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Robert Spangler [this message]
` Kirk Reiser
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=AEE30F68FCE5431A9DA5871E3160B045@dictat0r \
--to=spangler.robert@gmail.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).