public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: fedora core 7 speakup modified and dectalk express support
Date: Wed, 19 Sep 2007 18:20:50 -0600	[thread overview]
Message-ID: <001401c7fb1c$1a554380$210110ac@CHIHUAHUAL1> (raw)
In-Reply-To: <Pine.LNX.4.64.0709191716230.4145@dell.bellsouth.net>

Hi, Will this issue be fixed in the speakup version that works with 2.6.22 
for the dectalk express?  It would be nice if it were fixed.
----- Original Message ----- 
From: "Adam Myrow" <myrowa@bellsouth.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, September 19, 2007 4:20 PM
Subject: Re: fedora core 7 speakup modified and dectalk express support


> The Dectalk drivers are not broken.  It's the probing for the serial port
> that is the problem.  In the case of Slackware 12.0, which uses 2.6.21.5,
> it is necessary to pass the serial port on the command line.  For example,
> "speakup_synth=dectlk speakup_ser=0" would be right for a Dectalk Express
> on /dev/ttyS0.  So, try this with Fedora and others using 2.6.21.X
> kernels.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nick Gawronski
 ` Janina Sajka
   ` Adam Myrow
     ` Nick Gawronski [this message]
     [not found] ` <Pine.BSF.4.64.0709190940020.39405@server2.shellworld.net>
   ` a question about distro size? Karen Lewellen
     ` Kenny Hitt
     ` Littlefield, Tyler
       ` Karen Lewellen
     ` dan Murphy

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='001401c7fb1c$1a554380$210110ac@CHIHUAHUAL1' \
    --to=nick@nickgawronski.com \
    --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).