Source

Source

[Mike Ray]

Hello list,

I have been trying to get SpeakUp running and stable in the Raspbian 
(upstream Debian) and Arch Linux distros on the Raspberry Pi.

Initially I tried with the source from the SpeakUp web site and then 
discovered (ooops) that there is source present in:

linux/drivers/staging/speakup

And the source differs between the stable 3.6.11 source taken from the 
kernel repository on kernel.org and that in the 3.6.y source taken from 
the RPI foundation site.

Neither of these solutions is stable.  I get functionality, via espeakup 
but SpeakUp regularly crashes the kernel.

I'm waiting on a console cable so I can connect another machine to the 
kdb console on the Pi and read kernel oops or panic, and debug stuff 
from the kernel.

My question on here now is...am I missing something about the source of 
the source (if you see what I mean)?

The source from the SpeakUp repo is marked as 3.1.6 (I think) and not 
sure about what is in the kernel source.  The kernel source has patches 
applied for the changes to kernel serial IO made a few versions ago.

Mike

-- 
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK

Interested in accessibility on the Raspberry Pi?
Visit: http://www.raspberryvi.org/

 From where you can join our mailing list for visually-impaired Pi hackers

Re: Source

[Kirk Reiser]

Mike: The source for speakup has not been kept up to date in the
speakup git repo at linux-speakup.org since speakup was initiated into
the kernel staging tree. Someone needs to sync them once again but
nobody has. Whoever set-up the staging repo should have back ported
but that never happened either. Whether we resync them or not really
depends on what we decide to do with speakup for the future.


On Wed, 8 May 2013, Mike Ray wrote:

> Hello list,
>
> I have been trying to get SpeakUp running and stable in the Raspbian 
> (upstream Debian) and Arch Linux distros on the Raspberry Pi.
>
> Initially I tried with the source from the SpeakUp web site and then 
> discovered (ooops) that there is source present in:
>
> linux/drivers/staging/speakup
>
> And the source differs between the stable 3.6.11 source taken from the kernel 
> repository on kernel.org and that in the 3.6.y source taken from the RPI 
> foundation site.
>
> Neither of these solutions is stable.  I get functionality, via espeakup but 
> SpeakUp regularly crashes the kernel.
>
> I'm waiting on a console cable so I can connect another machine to the kdb 
> console on the Pi and read kernel oops or panic, and debug stuff from the 
> kernel.
>
> My question on here now is...am I missing something about the source of the 
> source (if you see what I mean)?
>
> The source from the SpeakUp repo is marked as 3.1.6 (I think) and not sure 
> about what is in the kernel source.  The kernel source has patches applied 
> for the changes to kernel serial IO made a few versions ago.
>
> Mike
>
>

-- 
Well that's it then, colour me gone!

Re: Source

[Mike Ray]

Hello Kirk,

First of all thanks for a great screen-reader.  Dependable when 
everything else turns to dust.

And thanks for clearing up the status of things as they are currently.

Until I came to the Raspberry Pi I had no reason to touch kernel 
development or debugging at all but as Linus said in an interview with 
the BBC; 'the Raspberry Pi makes falure affordable'.  It certainly makes 
it possible for me to brick enough installations to build a house.

But I can't get SpeakUp to run with any stability.  I suspect that's 
because of something fundamental about the platform.  But I'm pretty 
determined to get it going and bring accessibility to the Linux cli on 
the Pi.

If I can help in any way with updating the web site I'd be happy to do 
what I can.

Mike



On 08/05/2013 18:35, Kirk Reiser wrote:
> Mike: The source for speakup has not been kept up to date in the
> speakup git repo at linux-speakup.org since speakup was initiated into
> the kernel staging tree. Someone needs to sync them once again but
> nobody has. Whoever set-up the staging repo should have back ported
> but that never happened either. Whether we resync them or not really
> depends on what we decide to do with speakup for the future.
>
>
> On Wed, 8 May 2013, Mike Ray wrote:
>
>> Hello list,
>>
>> I have been trying to get SpeakUp running and stable in the Raspbian 
>> (upstream Debian) and Arch Linux distros on the Raspberry Pi.
>>
>> Initially I tried with the source from the SpeakUp web site and then 
>> discovered (ooops) that there is source present in:
>>
>> linux/drivers/staging/speakup
>>
>> And the source differs between the stable 3.6.11 source taken from 
>> the kernel repository on kernel.org and that in the 3.6.y source 
>> taken from the RPI foundation site.
>>
>> Neither of these solutions is stable.  I get functionality, via 
>> espeakup but SpeakUp regularly crashes the kernel.
>>
>> I'm waiting on a console cable so I can connect another machine to 
>> the kdb console on the Pi and read kernel oops or panic, and debug 
>> stuff from the kernel.
>>
>> My question on here now is...am I missing something about the source 
>> of the source (if you see what I mean)?
>>
>> The source from the SpeakUp repo is marked as 3.1.6 (I think) and not 
>> sure about what is in the kernel source.  The kernel source has 
>> patches applied for the changes to kernel serial IO made a few 
>> versions ago.
>>
>> Mike
>>
>>
>


-- 
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK

Interested in accessibility on the Raspberry Pi?
Visit: http://www.raspberryvi.org/

 From where you can join our mailing list for visually-impaired Pi hackers

Re: Source

[William Hubbs]

On Wed, May 08, 2013 at 01:35:02PM -0400, Kirk Reiser wrote:
> Mike: The source for speakup has not been kept up to date in the
> speakup git repo at linux-speakup.org since speakup was initiated into
> the kernel staging tree. Someone needs to sync them once again but
> nobody has. Whoever set-up the staging repo should have back ported
> but that never happened either. Whether we resync them or not really
> depends on what we decide to do with speakup for the future.

Kirk,

we should chat about this on irc; I have a way to sync them, but I don't
think I have push rights on the speakup repo any longer.

William

BBC interview

[Tony Baechler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Please contact me privately about this.  What BBC interview are you
talking about below?  I'm interested in hearing it.  I'm looking for
someone in the UK who is able to navigate the BBC site with Lynx and can
download radio programs from the BBC IPlayer.

On 5/8/2013 10:54 AM, Mike Ray wrote:
> Hello Kirk,
> 
> First of all thanks for a great screen-reader.  Dependable when
> everything else turns to dust.
> 
> And thanks for clearing up the status of things as they are currently.
> 
> Until I came to the Raspberry Pi I had no reason to touch kernel
> development or debugging at all but as Linus said in an interview with
> the BBC; 'the Raspberry Pi makes falure affordable'.  It certainly
> makes it possible for me to brick enough installations to build a
> house.
> 
> But I can't get SpeakUp to run with any stability.  I suspect that's
> because of something fundamental about the platform.  But I'm pretty
> determined to get it going and bring accessibility to the Linux cli on
> the Pi.
> 
> If I can help in any way with updating the web site I'd be happy to do
> what I can.
> 
> Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJRi04+AAoJEPrAuJWnLe0yfhMP/j7EfVWccxMMdLPcUuFa7eub
2Ies8xHSW7/IdjVgHGVlBSoh7CN0vu/w3hllsO7/OIK8FD0MbOhzp90Akt0yu0Ez
b0CSQQkxUiOf1xlPgodytlsl3/zydk+4RKx/4/AQ/rWElltwpnJhzYLziTWCuBeZ
G1QjCy8we3P2TvejSOKyNq6JAhqKD52H2oo7uIH9Mva7SjJ3VBiRKlI31z8H/xnt
HSW1KECo3qOZ75mMv0DGHy1CnJp7xs5be6PFVNIOsYJZLCzipSETccefk8O6CvPn
GCFreIzIrHpnG0t0LEQQYeUTO2rLfzswZv/2Jt3UWmLfo33Ke3xycyhTvQJJxYHZ
H9bQnFjA36D7sPsDy802pZ4ucV1ys6VPgyQ3G/c/kuG7PyhhAaxnoK3dxp1iwaIz
i1GtuHKMzmjAk4DzkOs/UccPr0zR2OEy6BhBYqDG9XTAlvZ3/ZCuRI/IoQ0OjTc3
Nq+dLpDhVhLqm6ti5Q+C835P9pLJWJttGMDiGMz3qJJciR3+EpDmPGpCMROP6JOx
O+oeKuaUJmPmwM4Yth8MswPlnpAKxl3Ihp38w9soRhJmlJ2EMYLGMbG1UD9ptJy1
Q/yGkDv+HelZGGZ/yP0uy5eBx7miEKD7WeFGEnlHxM3ZLE6BAVbEWopGL82HA3Ob
mtlE1cgqeO0RCpmDki8j
=UWsn
-----END PGP SIGNATURE-----

Re: Source

[Brandon McGinty-Carroll]

FYI,
Thanks to William, repos are synced.

Brandon McGinty-Carroll


On Wed, May 08, 2013 at 03:51:37PM -0500, William Hubbs wrote:
> On Wed, May 08, 2013 at 01:35:02PM -0400, Kirk Reiser wrote:
> > Mike: The source for speakup has not been kept up to date in the
> > speakup git repo at linux-speakup.org since speakup was initiated into
> > the kernel staging tree. Someone needs to sync them once again but
> > nobody has. Whoever set-up the staging repo should have back ported
> > but that never happened either. Whether we resync them or not really
> > depends on what we decide to do with speakup for the future.
> 
> Kirk,
> 
> we should chat about this on irc; I have a way to sync them, but I don't
> think I have push rights on the speakup repo any longer.
> 
> William
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Source

[Kirk Reiser]

On Wed, 8 May 2013, Mike Ray wrote:

> First of all thanks for a great screen-reader.  Dependable when everything 
> else turns to dust.

You are welcome. However, a lot of people other than I had major
contributions to speakup.

> And thanks for clearing up the status of things as they are currently.

Hahah, that remains to be seen.

> But I can't get SpeakUp to run with any stability.  I suspect that's because 
> of something fundamental about the platform.  But I'm pretty determined to 
> get it going and bring accessibility to the Linux cli on the Pi.

That is absolutely great. As far as I know, you are the first person
to report actually getting speakup to run on the Raspberry Pi. There
have been quite a few folks attempting it however. As you and others
have mentioned, some condition that regularly burks it is necessary
before much muscle can be brought to the fix. In general speakup is
very stable on most desktop and laptop machines, outside of a few
known problems.

> If I can help in any way with updating the web site I'd be happy to do what I
> can.

That is also great news. you can clone the website for linux-speakup.org with:

git clone http://linux-speakup.org/speakup-web.git

and have your way with it. Any changes you make you can send me a
patch and I'll apply it or give you an account you can make changes
directly, later on.

-- 
Well that's it then, colour me gone!

Re: Source

[Willem van der Walt]

Hi,
I now did a git pull to get the latest code and found that it gives the 
following error:
/home/wvdwalt/speakup/modules/../drivers/staging/speakup/speakup_soft.c: In function ‘softsynth_write’:
/home/wvdwalt/speakup/modules/../drivers/staging/speakup/speakup_soft.c:272:2: error: implicit declaration of function ‘kstrtoul_from_user’
make[2]: *** [/home/wvdwalt/speakup/modules/../drivers/staging/speakup/speakup_soft.o] Error 1
make[1]: *** [_module_/home/wvdwalt/speakup/modules/../drivers/staging/speakup] Error 2
make: *** [modules] Error 2

I am running 2.6.38-11-generic.
Do I need a later kernel for the latest speakup code or is this something 
else?
TIA, Willem

Re: Source

[Mike Ray]

Kirk,

Thanks, I'll take a look at the web stuff in a few days.  In the 
meantime I've now got some more to go on with finding the reason for the 
crash on the Raspberry Pi...

Yesterday I got a serial console cable through the post.  I connected it 
to the UART on a Raspberry Pi and for the first time have been able to 
trap the 'kernel oops' that occurs when SpeakUp crashes.

I get an 'unable to handle kernel NULL pointer dereference at' error.

Next I just need to learn how to use kdb, kgdb, gdb or a combination of 
all three to debug where this crash is occurring. As yet I don't know 
how to be able to trace back through the source to find the error.  I 
could just put a bunch of 'printk' calls in the source I guess but I am 
not sure if that will slow things down too much.

I am following the forwarded messages from the kernel guys with 
interest.  It is good to see that there still efforts to push things 
forward.  I'd also be happy to do some of the clean-up tasks.  I've 
written tons of Perl in my time and it strikes me that changing some of 
the variable names and stuff could be automated.

Mike



On 10/05/2013 02:55, Kirk Reiser wrote:
> On Wed, 8 May 2013, Mike Ray wrote:
>
>> First of all thanks for a great screen-reader.  Dependable when 
>> everything else turns to dust.
>
> You are welcome. However, a lot of people other than I had major
> contributions to speakup.
>
>> And thanks for clearing up the status of things as they are currently.
>
> Hahah, that remains to be seen.
>
>> But I can't get SpeakUp to run with any stability.  I suspect that's 
>> because of something fundamental about the platform.  But I'm pretty 
>> determined to get it going and bring accessibility to the Linux cli 
>> on the Pi.
>
> That is absolutely great. As far as I know, you are the first person
> to report actually getting speakup to run on the Raspberry Pi. There
> have been quite a few folks attempting it however. As you and others
> have mentioned, some condition that regularly burks it is necessary
> before much muscle can be brought to the fix. In general speakup is
> very stable on most desktop and laptop machines, outside of a few
> known problems.
>
>> If I can help in any way with updating the web site I'd be happy to 
>> do what I
>> can.
>
> That is also great news. you can clone the website for 
> linux-speakup.org with:
>
> git clone http://linux-speakup.org/speakup-web.git
>
> and have your way with it. Any changes you make you can send me a
> patch and I'll apply it or give you an account you can make changes
> directly, later on.
>


-- 
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK

Interested in accessibility on the Raspberry Pi?
Visit: http://www.raspberryvi.org/

 From where you can join our mailing list for visually-impaired Pi hackers

Re: Source

[Chris Brannon]

Mike Ray <mike@raspberryvi.org> writes:

> Kirk,
>
> Thanks, I'll take a look at the web stuff in a few days.  In the
> meantime I've now got some more to go on with finding the reason for
> the crash on the Raspberry Pi...
>
> Yesterday I got a serial console cable through the post.  I connected
> it to the UART on a Raspberry Pi and for the first time have been able
> to trap the 'kernel oops' that occurs when SpeakUp crashes.
>
> I get an 'unable to handle kernel NULL pointer dereference at' error.

Mike,
Was there a stack trace along with that error?  If so, I'd like to see
it.

-- Chris