From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: Which hardware synthesizer to buy?
Date: Mon, 13 Apr 2009 16:13:09 -0500 [thread overview]
Message-ID: <20090413211309.GA20121@linux1> (raw)
In-Reply-To: <20090413182256.GA24586@localhost.localdomain>
On Mon, Apr 13, 2009 at 11:22:56AM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, Apr 13, 2009 at 08:47:51AM -0400, Kirk Reiser wrote:
> > Even with a hardware synth we have nowhere near a power-up to shutdown
> > solution like we used to have.
>
> I must say I was surprised when I read that. I've been using speakup
> since the 0.09 days, and haven't noticed any less bootup, or shutdown
> messages than before. I will admit though that I don't follow bootup
> and shutdown messages from start to finish, unless I have a specific
> reason to do so. As far as I know, having speakup and my synth driver
> built into the kernel, still gives me speech from what sounds like
> early on in the boot process, until the machine powers off, just like
> it always used to, or so it has seemed to me up until now. So, what
> have I overlooked, and am not aware of?
Greg,
you are correct about having speakup and the synth driver built in
giving you speech early in the boot process. However, it is not as
early as it was with the older kernels, and I personally do not know of
a way that we will be able to come up that early at this point.
We made this change because of a bug that would cause the serial ports
that speakup was not using to be numbered incorrectly, for example, if
your synthesizer was on ttyS0 and you started speakup built in, ttyS1
would be renumbered to ttyS0, but it would not be renumbered if you did
not start speakup or if it was not built in. This was caused because
speakup was being started before the kernel's serial driver.
For newer kernels (I believe 2.6.26 or later when the accessibility
drivers first appeared), we are installing as an accessibility driver if
you build speakup into the kernel, and we are starting late enough that
this is not an issue.
Let me know if that makes sense.
William
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Gaijin
` Nick Stockton
` Gaijin
` Kirk Reiser
` John covici
` al Sten-Clanton
` Gregory Nowak
` William Hubbs [this message]
` John covici
` William Hubbs
` John covici
` Gregory Nowak
` William Hubbs
` Chris Brannon
` Gregory Nowak
` Chris Brannon
` Gregory Nowak
` Alex Snow
` virtualization, was: " Gregory Nowak
` Alex Snow
` Gregory Nowak
` Gaijin
` Garrett Klein
` Janina Sajka
` Gaijin
` William Hubbs
` Tony Baechler
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=20090413211309.GA20121@linux1 \
--to=w.d.hubbs@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).