Gentoo Archives: gentoo-accessibility

From: Robyn Dawn Hannigan <sonofthejedi@×××××××.nz>
To: gentoo-accessibility@l.g.o
Subject: Re: [gentoo-accessibility] speakup and 2.6.37 on gentoo
Date: Sat, 12 Feb 2011 12:28:47
Message-Id: 362087.60574.qm@web96115.mail.aue.yahoo.com
In Reply to: [gentoo-accessibility] speakup and 2.6.37 on gentoo by William Hubbs
1 > From: William Hubbs <williamh@g.o>
2 > To: gentoo Accessibility <gentoo-accessibility@l.g.o>
3 > Cc: speakup mailing list <speakup@×××××××××××.ca>
4 > Sent: Wed, 2 February, 2011 5:30:56 AM
5 > Subject: [gentoo-accessibility] speakup and 2.6.37 on gentoo
6 >
7 > All,
8 >
9 > gentoo-sources-2.6.37 is in our tree. I do not know when it will be
10 > marked stable, but I wanted to go ahead and post a message about the
11 > upgrade process for speakup users.
12
13 > When you configure a 2.6.37 or newer kernel, you will find speakup in
14 > the staging drivers under device drivers in the menu. Be sure to select
15 > the speakup core and the synthesizer driver(s) you need. They can either
16 > be modules or built in.
17 >
18 > Once the new kernel is compiled and installed, you should be able to
19 > boot normally and have speakup start talking.
20
21 ... snip ...
22
23 Hello List,
24
25 Congratulations on finally getting this to staging! 5 years is a lot of
26 patience from the developers. So before anything, all users and hackers
27 deserve many compliments.
28
29 What doers the software synthesizers stack look like now? Is there any
30 interest in it being tested or is it no longer a viable option?
31
32 It used to look like
33 kernel
34 |+ speakup.ko with speakup_soft
35 |+ speakup_soft with parameter start=1
36 |+ espeak installed on system with USE=portaudio
37 |+ speakup package installed on system
38 |+ speech-dispatcher installed on system
39 |+Add speech-dispatcher to a runlevel a
40 |+Add espeakup to runlevel a
41
42 This worked for a while but stopped in kernel 2..6.32 or so. i tried again
43 a few weeks ago, but speech-dispatcher seems to be not working any longer
44 on ~amd64. If anyone has any idea what the current stack looks like, i
45 would appreciate some pointers. For obvious reasons links websites are
46 preferred but if this is still 'in the back room' then perhaps we might
47 start something about this on the accessibility project page?
48
49 Depends if there is any interest.
50
51 All the best anyway,
52 rdh