From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wlym.com (wlym.com [66.135.63.43]) by speech.braille.uwo.ca (Postfix) with ESMTP id 522A4C1A21D for ; Fri, 4 Mar 2011 16:22:06 -0500 (EST) Received: from ccs.covici.com (pool-71-171-100-42.clppva.fios.verizon.net [71.171.100.42]) (authenticated bits=128) by wlym.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id p24LM3d3022600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 4 Mar 2011 15:22:05 -0600 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.4/8.14.4) with ESMTP id p24LLxQm019074 for ; Fri, 4 Mar 2011 16:22:02 -0500 To: "Speakup is a screen review system for Linux." Subject: Re: Serial conflict In-reply-to: <20110304210013.GA8385@rivensight.dyndns.org> References: <4D6DAAFE.7020201@gmail.com> <20110302110133.GA6917@rx.westell.com> <4D6E808D.6040207@gmail.com> <20110302212017.GB17303@lnx3> <4D6EB855.90302@gmail.com> <4D710EF6.5000209@gmail.com> <0E09BE0B-6C24-413A-ABAE-BD79FB91DFB0@speedpost.net> <20110304210013.GA8385@rivensight.dyndns.org> Comments: In-reply-to Frost message dated "Fri, 04 Mar 2011 21:00:13 +0000." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.2.1 Date: Fri, 04 Mar 2011 16:21:59 -0500 Message-ID: <19072.1299273719@ccs.covici.com> From: covici@ccs.covici.com X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.13 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 21:22:06 -0000 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 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 # http://rivensight.dyndns.org > Postings Copyrighted 2010-2011 by: Michael Ferranti > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com