public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Albert Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Serial conflict
Date: Fri, 04 Mar 2011 12:16:38 -0500	[thread overview]
Message-ID: <E70C112CB1D84F1B9B8DEC5F057E2737@ownercb76d9f6c> (raw)
In-Reply-To: <0E09BE0B-6C24-413A-ABAE-BD79FB91DFB0@speedpost.net>

Would this influence how early in the boot-up Speakup could kick in using a
hardware synthesizer?  I'm sorry to say I know nothing about this area.
Thanks!

Al 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Zachary Kline
Sent: Friday, March 04, 2011 11:12 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Serial conflict

This is an excellent suggestion, if at all practical.  If we did this it
might also let us handle USB serial ports and the like with ease, since we'd
then be in userspace.
Hope we can make something of it,
Zack.
On Mar 4, 2011, at 8:10 AM, Christopher Moore wrote:

> Hello,
> Here's another thought:  Suppose we did away with all the hardware synth
modules in speakup.  All interaction with speakup could be done through the
/dev/softsyn device.  This would require converting the hardware modules to
user-space programs which would communicate with speakup over the
/dev/softsyn device and to the hardware synth over the /dev/tts serial
device.
> 
> What I'm suggesting is to remove serial port support from speakup since it
appears to be problematic at best.
> 
> Chris
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jacob Schmude
 ` covici
   ` Jacob Schmude
 ` Chuck Hallenbeck
   ` Jacob Schmude
     ` Steve Holmes
       ` Jacob Schmude
         ` Steve Holmes
           ` Christopher Brannon
             ` Steve Holmes
         ` Christopher Moore
           ` Zachary Kline
             ` Albert Sten-Clanton [this message]
               ` David Csercsics
             ` Frost
               ` covici
           ` speakup in user space (was Re: Serial conflict) Jacob Schmude
             ` William Hubbs
               ` Jacob Schmude
                 ` Steve Holmes
                   ` Kyle
                 ` Jason White
                   ` Jason White
                 ` Ari Moisio

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=E70C112CB1D84F1B9B8DEC5F057E2737@ownercb76d9f6c \
    --to=albert.e.sten_clanton@verizon.net \
    --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).