From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo drops speakup
Date: Mon, 16 Jul 2007 17:42:23 -0700 [thread overview]
Message-ID: <20070717004223.GA1937@localhost.localdomain> (raw)
In-Reply-To: <035601c7c7f6$450dc100$4ba65c90@vv507j>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Jul 16, 2007 at 05:11:33PM -0500, John Heim wrote:
> Kirk, I know you're busy and I hate to ask but do you think you could give a
> brief status report? Is speakup ever going to be in the main kernel source
> tree? Of course, I understand these things take time but I was just
> wondering if there is a problem.
I'm not Kirk, but from what I understand, speakup isn't in the
mainstream kernel source, because the kernel developers think the code
is badly written, and it doesn't meet their standards.
As for whether or not speakup will be a part of the kernel tree, I
hate to be blunt and direct, but I think the question to ask before
that one as of now, is whether speakup will work ever again or not? I
know all of us would probably say yes, and it probably will, but it
isn't going to magically happen. From what I've seen in the gentoo bug
description, the main show stopper now is speakup's serial code, and
as far as I can tell, fixing that will mean either rewriting how
speakup probes for a serial synth (which doesn't sound and probably
isn't simple), or putting a part of, or all of speakup into user
space.
No, I'm not volunteering. Like a couple of people here said, I too have
looked at the speakup code in the past. While I have a vague inkling
of what's happening, I don't understand enough about kernel internals
myself to write the same thing from scratch, or probably to even
attempt successfully modifying it. Yes, I know I could learn kernel
programming, but that would take time, and time, like many of us,
isn't something I happen to have right now.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGnBBv7s9z/XlyUyARAhoAAJwMmRL59W9DTZ/3Vjn4LvLXCCN1sACgz8HG
d2RRGj2OG9fiGsJwhzQAqbk=
=MRIz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
josh
` Luke Yelavich
` Zachary Kline
` Ralph W. Reid
` Gregory Nowak
` John Heim
` Chuck Hallenbeck
` Kirk Reiser
` Albert E. Sten-Clanton
` Georgina Joyce
` John Heim
` Gregory Nowak [this message]
` Travis Siegel
` Joseph C. Lininger
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=20070717004223.GA1937@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).