From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zcs.mccainsystems.com (zcs.mccainsystems.com [23.23.221.81]) by befuddled.reisers.ca (Postfix) with ESMTP id 75B181EF6B0 for ; Wed, 8 May 2013 16:53:51 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs.mccainsystems.com (Postfix) with ESMTP id DF94A13B8FB for ; Wed, 8 May 2013 16:53:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs.mccainsystems.com Received: from zcs.mccainsystems.com ([127.0.0.1]) by localhost (zcs.mccainsystems.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iyu06-RjqTg for ; Wed, 8 May 2013 16:53:48 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs.mccainsystems.com (Postfix) with ESMTP id 0FC5813328E for ; Wed, 8 May 2013 16:53:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs.mccainsystems.com Received: from zcs.mccainsystems.com ([127.0.0.1]) by localhost (zcs.mccainsystems.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PGRH9QybDcFO for ; Wed, 8 May 2013 16:53:46 -0400 (EDT) Received: from ip-10-122-162-135.ec2.internal (zaria.coolip.net [50.16.211.118]) by zcs.mccainsystems.com (Postfix) with ESMTPSA id EA2AF13B8FB for ; Wed, 8 May 2013 16:53:46 -0400 (EDT) Date: Wed, 8 May 2013 16:53:45 -0400 (EDT) From: Kelly Prescott To: "Speakup is a screen review system for Linux." Subject: Re: the direction of speakup In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.15 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: Wed, 08 May 2013 20:53:51 -0000 I am certainly not a hardware expert, but Xen VmWare etal control the hardware as is. Now, they don't intercept the video at least I don't think they do, but the UEFI specification allows for things to run before boot and that is why I thought we might be able to do something with that. Remember the Speaqualizer back in the 1980's which read the hardware directly? Maybe we could have 2 parts to speakup... first takes over at the boot process and then a module gets loaded later to provide more functionality. this reads the boot and hardware kernel messages as well as providing for userspace support. On Wed, 8 May 2013, acollins@icsmail.net wrote: > I doubt that would work, I'm not familiar with uefi, but it would have > have to intercept all the kernels hardware video calls in order to speak > while the kernel is running. Do you know what hardware specs the uefi > spec has? > > Gene > >> Maybe the UEFI specification can help us. >> What about a small UEFI application to be a screen reader then launch the >> kernel or what ever. >> This would not work for older systems, but might get around the kernel >> driver problem as the reader encapsulates the kernel so to speak. >> >> >> On Wed, 8 May 2013, Martin G. McCormick wrote: >> --- anip --- >>> A Unix kernel is the master process and everything else >>> that happens on your system is spawned as a subprocess of the >>> master. Would it be possible to have a kernel equipped with >>> speakup spawn the rest of one's system as if it was a virtual >>> system? That could take care of the I/O. >> _______________________________________________ >> Speakup mailing list >> Speakup@linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >