From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by speech.braille.uwo.ca (Postfix) with ESMTP id 33134C1A25F for ; Fri, 4 Mar 2011 22:22:09 -0500 (EST) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Pvi4G-0002Ts-9j for speakup@braille.uwo.ca; Sat, 05 Mar 2011 04:22:08 +0100 Received: from ppp198-218.static.internode.on.net ([59.167.198.218]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Mar 2011 04:22:08 +0100 Received: from jason by ppp198-218.static.internode.on.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Mar 2011 04:22:08 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: speakup@braille.uwo.ca From: Jason White Subject: Re: speakup in user space (was Re: Serial conflict) Date: Sat, 5 Mar 2011 03:21:50 +0000 (UTC) Message-ID: References: <4D6DAAFE.7020201@gmail.com> <4D712A35.1020806@gmail.com> <20110304185255.GA28217@linux1> <4D715177.3090306@gmail.com> X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ppp198-218.static.internode.on.net X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: jason@jdc.jasonjgw.net (Jason White) 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: Sat, 05 Mar 2011 03:22:09 -0000 Jacob Schmude wrote: >I don't think that's a limitation of the VCSA devices themselves, but >rather how they are used. These devices show the screen as it >currently is at any given time, although documentation for them is >rather sparse. But couldn't we, rather than querying the device, >monitor it instead for incoming text? I'll do some digging and see >what I can find out. Even if the VCSA devices have such a limitation, you could propose changes to overcome it, or write a relatively simple kernel module just to expose the necessary information and implement the screen reader itself in user space. >It just seems that to have speakup in the kernel even after removing >serial support would leave us with all of the problems with none of >the advantages remaining. As I understand the situation, keystrokes can be intercepted from user space as well now; support for this was integrated into BRLTTY relatively recently. If I were designing a screen reader for Linux, I wouldn't put it in the kernel unless there were really no workable alternative. If I had to touch the kernel, it would be by way of a minimal driver just to provide the necessary interfaces.