From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by speech.braille.uwo.ca (Postfix) with ESMTP id 39D32C1A0E9 for ; Fri, 4 Mar 2011 12:59:53 -0500 (EST) Received: from pd2ml2so-ssvc.prod.shaw.ca ([10.0.141.134]) by pd4mo1so-svcs.prod.shaw.ca with ESMTP; 04 Mar 2011 10:59:52 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=I0jFHxriRJwyplOnjK2nOSNCO7GacXBAI5CCNqI8fuI= c=1 sm=1 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=kNJomTX52Cr8WCRvCvE+DQ==:17 a=v62ou_fjodM6h66ayFUA:9 a=Xk1Hy8q1qSz1S3IkHAlxGYlLJbIA:4 a=CjuIK1q_8ugA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO really.lan) ([174.4.134.251]) by pd2ml2so-dmz.prod.shaw.ca with ESMTP; 04 Mar 2011 10:59:43 -0700 Date: Fri, 4 Mar 2011 09:59:43 -0800 From: David Csercsics To: "Speakup is a screen review system for Linux." Subject: Re: Serial conflict Message-ID: <20110304175943.GA12321@really.lan> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 17:59:53 -0000 On Fri, Mar 04, 2011 at 12:16:38PM -0500, Albert Sten-Clanton wrote: > Would this influence how early in the boot-up Speakup could kick in using a > hardware synthesizer? I'm sorry to say I know nothing about this area. It shouldn't provided we keep the userspace programs small enough to be contained nicely on a ramfs. This is what the kernel's early userspace stuff is designed for. Going to make building custom kernels a bit more of a pain and there will need to be init scripts to start the synth program back up after the system has properly transferred control to the real root file system but you could make that happen very early so you'd only lose speech for less than a second unless there's some error or other with the boot process which likely means you'll need to pull out your rescue CD to fix it anyway.