From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo dropping speakup support
Date: Sun, 17 Jun 2007 23:22:19 +0100 [thread overview]
Message-ID: <1182118939.3634.15.camel@layla.Mshome> (raw)
In-Reply-To: <20070617200022.GA16786@linux1>
While it is a shame that you find this, thank you for saying what the
exact problem is. If speakup won't compile on x86-64 either now, I am
sure that soon someone will fix that as it probably affects quite a
number of users.
Other than the install of gentoo, I don't think the impact is as bad as
it is for other distros as gentoo users may tend to want to compile a
custom kernel anyway. The install probably isn't such a problem as I
think if you are doing an install from the internet then it doesn't
matter what version of gentoo the CD is as the installed system will be
the latest, so a user could use the last release with speakup to install
with speakup (unless they are doing an install without internet access,
for which there may not be a solution).
On a different note, while I don't know enough about the kernel to be
certain, but is this problem to do with speakup and the way it accesses
the serial ports? As I remember from some previous discussions about
speakup and serial port access, I think it was said that if speakup used
the standard serial port driver then it should be possible to use serial
ports not built on the motherboard. So would this also help in solving
such a problem as found in gentoo? If so might it be time to say it must
be done?
Unfortunately I currently cannot help with this as I am a python
programmer so would need to learn C before I could do anything, probably
something I should do as so much opensource software is written in C.
From
Michael Whapples
On Sun, 2007-06-17 at 15:00 -0500, William Hubbs wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> because of this bug [1], gentoo linux will be dropping support for speakup in its official kernels starting at 2.6.22.
>
> [1] http://bugs.gentoo.org/show_bug.cgi?id=177794
>
> Is there any possibility at all that speakup could be moved into user space as the bug suggests? I feel that if we can go into user space this will b a better approach.
>
> Thanks,
>
> - --
> William Hubbs
> gentoo accessibility team lead
> williamh@gentoo.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFGdZLWblQW9DDEZTgRAsCOAJoD/roDmHTKu7ji8qTXZ2eoX47T1ACeIivJ
> j/qhb9Z6KNpfitEvr7Onrug=
> =mpb2
> -----END PGP SIGNATURE-----
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs
` Zachary Kline
` Sina Bahram
` Gaijin
` Tom Moore
` Michael Whapples [this message]
` Deedra Waters
` Travis Siegel
` Zachary Kline
` C.M. Brannon
` Doug Sutherland
` Deedra Waters
` Travis Siegel
` Gaijin
` Doug Sutherland
` Luke Yelavich
` Jim Grimsby Jr.
` Doug Sutherland
` Gaijin
` Doug Sutherland
` Michael Whapples
` Lorenzo Taylor
` Samuel Thibault
` Travis Siegel
` Gaijin
` John covici
` Luke Yelavich
Keith Hinton
` James Homuth
` Gaijin
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=1182118939.3634.15.camel@layla.Mshome \
--to=mwhapples@aim.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).