Well, I am thinking that removing the dtlk and the rest shouldn't be to hard since it's modularized from what I've seen of the code. Perhaps it's time to do some architecture modularization as well? Maybe lift out some of the x86 specific stuff and do what the kernel does, with an arch folder and then arch specific code under there. I'm not really sure how that'd be done with the modules and the compilation process, but it seems like it could be doable. On 2/20/2012 7:26 PM, Kerry Hoath wrote: > > Speakup communicates with x86 hardware directly. Careful about out of > the box optimism you might have to modify or remove all the hardware > specific modules. > there also may be timer tick issues. > > regards, Kerry. > > On 21/02/2012 9:25 AM, Kyle wrote: >> I didn't think Arch would run on Arm at all, since according to their >> website, only x86 and x86_64 are supported, but apparently Raspberry Pie >> will be supporting ArchLinux as soon as the board is released. As for >> Speakup, since it is a set of Linux kernel modules, it should compile on >> Arm with no problem. Also, as far as I know, eSpeak shouldn't have any >> trouble compiling for Arm either, and this may have already been tested. >> As far as I know, it runs successfully on most, if not all, Android >> devices, and a quick Google showd an eSpeak Debian package for the Arm >> architecture as well. And yes, for $35, I will probably be one of the >> many of us who will play with this thing. >> ~Kyle >> _______________________________________________ >> Speakup mailing list >> Speakup at braille.uwo.ca >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Take care, Ty Web: http://tds-solutions.net The Aspen project: a light-weight barebones mud engine http://code.google.com/p/aspenmud Sent from my toaster.
