From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from d-out-001.smtp25.com (d-out-001.smtp25.com [67.228.158.174]) by befuddled.reisers.ca (Postfix) with ESMTPS id C4C9A1EF08B for ; Thu, 2 May 2013 03:22:35 -0400 (EDT) Received: from ccs.covici.com (ccs.covici.com [70.109.53.110]) by d-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id r427MVuB002673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 2 May 2013 03:22:31 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.6/8.14.5) with ESMTP id r427MUNP008022 for ; Thu, 2 May 2013 03:22:31 -0400 To: "Speakup is a screen review system for Linux." Subject: Re: the direction of speakup In-reply-to: References: Comments: In-reply-to acollins@icsmail.net message dated "Wed, 01 May 2013 23:42:38 -0500." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.2 Date: Thu, 02 May 2013 03:22:30 -0400 Message-ID: <8021.1367479350@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: d-out-001.smtp25.com-r427MVuB002673 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: Thu, 02 May 2013 07:22:36 -0000 If we gave up the kernel, which I would really prefer not to do, then we could use speech dispatcher and write drivers for the serial synths or usb ones. But this is to be decided. acollins@icsmail.net wrote: > Hello all. If Speakup were a user space app, you could start it from > inittab, like you can brltty. It would also be able to access the video > scrollback buffer. > > I don't think the support for isa synths needs to go away just yet. > Believe it or not, there are still a few folks running older machines with > isa slots with isa synths in them. Besides this, for those who really > want them, it is still possible to buy machines with isa slots, so if > you have an isa synth, you can use it in a new machine. So I don't > think it's time to drop isa support yet. > > Having said that, adding usable usb serial, and support for usb synths > should be a priority. At this point, I find myself ambivalent about > whether speakup stays in the kernel or not. You don't get any better > access to boot messages with software speech than you could from user > space. If the user space Speakup could be started from inittab, then > you could still get info about file system checks and such. The only > thing you couldn't get, which you can't get with software speech either, > is kernle panic errors. With Speakup in the kernel, and using a > hardware synth, you can sometimes still get that info, depending on how > the kernel panics. There have been a couple of times when this has been > a life saver for me, but it happens so rarely, that I could probably > live with the inconvenience. Thus I'm finding myself ambivalent about > Speakup staying in the kernel. But then I'm getting older, and > ambivalent about a lot of things. (grin) > > Gene Collins > > >hmmm, I wonder if we could just add a kernel driver as though we were > >writing one for a new serial card that way we would conform to what the > >kernel devs want? From within that, maybe you could specify the way to > >get the device to use, or maybe have some simple user space program to > >tell it the device -- this is way off the top of my head, but is > >interesting to me. You could write drivers for speech dispatcher for > >serial synths, but getting that into an initramfs would be difficult, > >you would have to change the generation scripts for each distribution, > >etc. > > > >my $.02 (or .2 trillion with hyperinflation). > > > >William Hubbs wrote: > > > >> All, > >> > >> let's start a new thread here to figure out what needs to be done with > >> speakup. > >> > >> Here are my ideas and the issues I see with them: > >> > >> 1. What should we do with support for the internal ISA synthesizers? > >> > >> My thought is that these can be dropped. > >> > >> 2. We basically have two choices for the serial synthesizer issues. > >> > >> a. If we keep this code inside the kernel, the bottom line is it needs > >> to be completely rewritten and there need to be changes made on the > >> kernel side to make it work correctly. > >> This will take time, and someone here will need to > >> work closely with the kernel developers, and we'll need to find someone > >> in the kernel community to guide us -- maybe not by writing the code for > >> us, but at least consulting with us. > >> > >> b. If we move this code into user space, we can code it however we want, > >> and that frees us from involving the kernel team. > >> > >> question: > >> > >> If we move the serial code to user space, I realize there is a concern > >> about missing early boot messages. Would putting the user space daemon > >> into an initramfs solve this? would you be able to start it early > >> enough to get all of the boot messages if it was in an initramfs? > >> > >> William > >> > >> _______________________________________________ > >> Speakup mailing list > >> Speakup@linux-speakup.org > >> http://linux-speakup.org/cgi-bin/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 > >_______________________________________________ > >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 -- 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