From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ccs.covici.com ([67.62.15.196]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1IEtyI-0004uk-00 for ; Sat, 28 Jul 2007 17:37:10 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.0/8.13.7) with ESMTP id l6SLb72K012454 for ; Sat, 28 Jul 2007 17:37:10 -0400 Received: (from covici@localhost) by ccs.covici.com (8.14.0/8.13.7/Submit) id l6SLb78f012448; Sat, 28 Jul 2007 17:37:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18091.46850.912319.256676@ccs.covici.com> Date: Sat, 28 Jul 2007 17:37:06 -0400 From: John covici To: "Speakup is a screen review system for Linux." Subject: speakup, 2.6.22, and the way forward In-Reply-To: <46A80FB9.4070504@gentoo.org> References: <46A80FB9.4070504@gentoo.org> X-Mailer: VM 7.17 under Emacs 22.0.95.1 X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 Precedence: list Reply-To: covici@ccs.covici.com, "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: Sat, 28 Jul 2007 21:37:11 -0000 And that is the problem -- I wonder if there is any way to do both -- after all the serial console must be done pretty early in the process and maybe we could switch to some other access method later on? If we can't get the early boot messages or other kernel information, then speakup may as well be in user space altogether, but that would be a real sad thing for me at any rate. Maybe speakup can't ever be included in the mainstream kernel because of these strange requirements -- I am not sure. -- 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