public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo dropping speakup support
Date: Sun, 17 Jun 2007 23:39:53 -0500	[thread overview]
Message-ID: <00c601c7b162$b7184180$ab00a8c0@tenstac> (raw)
In-Reply-To: <03BC5C96-1E28-4336-B323-8C3FC6ED1BEE@softcon.com>

Travis,

I wasn't suggesting that this was addressing the real problem,
as I said, it was a suggestion as interim way to at least have 
speech if  the regular boot doesn't talk. 

The problem is bigger than user space or not. Right now you
cannot grab a doubletalk LT and plug it into a USB serial 
adapter and use speakup, or any RS232 synth. 

Interestingly though, you can plug a doubletalk LT into USB
serial adapter and configure the kernel for usb serial console
and get ALMOST all of the boot messages, but speakup 
will not work.

The days of having RS232 ports on PCs might be limited, 
and  there's lots of RS232 synths around, so this is an 
example where the real answer lies in at mininal some 
re-architecture of the speakup driver.  

I'm perhaps a bit over the edge here, but I like to think 
a lot in the multimodal sense that its always a bad idea 
to assume specific modality, like a PC keyboard for 
example. What I would like to see happening in speech 
and accessibility in general is generic interfaces that do 
not assume specific device. The synth has functions that
you invoke with keyboard, now let's say it was on a 
phone with 4x4 keypad, or on a remote control, it 
would be nice if it could still be doable. So basically 
rather than assuming 104 key keyboard that would be
one mapping of function to controller. 

There seems to be several good arguments for 
re-architecting the drivers in this way, on both the 
synth and user ends of the whole. 

The kernel versus user space argument is interesting.
Consider ALSA, you have kernel drivers, but you 
also have apps that use those drivers like the config
apps and the mixers and players. I tend to think that
strategically speakup needs to move in that direction.

Tactically my suggestion was coming up with some 
small easily installable root file system and kernel 
that would enable speech for those who don't have
it working, which from watching this list for several
years, seems to be many people.

What would be really cool is a USB dongle that 
is not only a speech system but an entire linux 
system on flash too. You could boot it on a 
windows machine and not use windows at all.
And ideally it would also work with windows.
Okay, now back to reality, I'd be happy just to 
figure out how to solve the usb serial problem
in the near term.

  -- Doug



----- Original Message ----- 
From: "Travis Siegel" <tsiegel@softcon.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, June 17, 2007 10:16 PM
Subject: Re: gentoo dropping speakup support


> Doug.
> Your suggestion of having a small installation on the machine is a  
> good one, and it probably would work.  However, this assumes you  
> already know what the problem is that needs fixed.  Without having  
> access to the actual boot messages (not just the ones you see while  
> booting into your sandbox as it were) you'll never be able to solve   
> any major problems that crop up in regards to the main system.
> it is however, not a bad idea, since it would allow some degree of  
> free usage w/o sighted assistance on simple fixes.  it wouldn't  
> address the  main issue though.
> And, in any case, it's functionally equivalent to the original  
> suggestion of using a live cd to boot and work on fixing the issues  
> from there.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  parent reply	other threads:[~ UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs
 ` Zachary Kline
   ` Sina Bahram
   ` Gaijin
 ` Tom Moore
 ` Michael Whapples
   ` Deedra Waters
     ` Travis Siegel
       ` Zachary Kline
         ` C.M. Brannon
       ` Doug Sutherland
         ` Deedra Waters
         ` Travis Siegel
           ` Gaijin
             ` Doug Sutherland
               ` Luke Yelavich
                 ` Jim Grimsby Jr.
           ` Doug Sutherland [this message]
             ` Gaijin
               ` Doug Sutherland
                 ` Michael Whapples
                   ` Lorenzo Taylor
                     ` Samuel Thibault
                     ` Travis Siegel
                     ` Gaijin
 ` John covici
 ` Luke Yelavich
 Keith Hinton
 ` James Homuth
 ` Gaijin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00c601c7b162$b7184180$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).