Serial conflict

covici at covici at
Fri Mar 4 16:21:59 EST 2011

I agree, don't take speakup out of the kernel -- I had something the
other day, where I had the wrong ramdisk version and it would not load
any modules, but I had speakup -- since  my synth is built into the
kernel and was able to figure out what happened -- if speakup were in
user space I would have been sunk.

But how about the following -- can we put a notify into the serial synth
initialization so speakup would know when things were happening and
could simulate an open for whatever device, or steal the port before the
serial synth could do anything -- prefer the former if possible.

Frost <znvyyvfgf at> wrote:

> On Fri, Mar 04, 2011 at 08:12:23AM -0800, Zachary Kline wrote:
> > This is an excellent suggestion, if at all practical.  If we did this 
> > it might also let us handle USB serial ports and the like with ease, 
> > since we'd then be in userspace.
> 	Then what's the point of getting SpeakUP into the kernel.  And 
> what about "power-of to power-off support.  How is ANY blind linux user 
> going to manage to fsck a disk when needed.  We might as well go back to 
> friggin yasr.
> 	We just got SpeakUP into the kernel and may soon be getting 
> support from other kernel developers to support serial ports properly 
> from kernelspace, and you want to ditch it all and go back to 
> prehistoric SpeakUP and scratching at fleas.
> 	You people disgust me.
> 				Michael
> --
> Linux User:	177869 # Powered By: Intel #
>           Postings Copyrighted 2010-2011 by: Michael Ferranti
> _______________________________________________
> Speakup mailing list
> Speakup at

Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici at

More information about the Speakup mailing list