public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Steve Holmes <steve@holmesgrown.com>
To: speakup@braille.uwo.ca
Subject: Re: Serial conflict
Date: Thu, 3 Mar 2011 09:18:28 -0700	[thread overview]
Message-ID: <20110303161828.GA21823@lnx3> (raw)
In-Reply-To: <4D6EB855.90302@gmail.com>

Yeah, mine too.  I never delved into kernel programming either.  Maybe
it isn't all that hard but I don't know where to start in that world.
The thing that bugs me here with the serial port problems is that this
stuff seems to work on some people's machines and not on others.
Where I run into serial issues is on a machine that apparently has 64
bit capability but at the time I built my Arch installation, I hadn't
realized it so it is basically built as a 32 bit system (x86). Hey, I
might try the speakup-enabled Arch live CD; wonderif I can override
the speakup.synth parameter on that; never tried so far.

Chris, can one do that with your live CD? if so, what name is used for
the image or first word of the command line?  I guess I could inspect
the grub lines you have on that disk to figure that out.

On Wed, Mar 02, 2011 at 01:36:21PM -0800, Jacob Schmude wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Steve
> I'm glad I'm not the only one, though I know that doesn't help. It's
> definitely not the speakout driver in this case. I don't have one, but
> I do have a doubletalk lt, accent sa, and dectalk express, all of
> which I've tried. I'd try my Keynote SA as well except Speakup doesn't
> support that one.
> I understand the hope of better serial support, though I think the
> logic is flawed. I remember once before when speakup/kernel
> integration was being pursued, and one of the reasons it didn't get in
> was because of its self-contained and ancient serial stack. However,
> expecting others to help--others who, I might add, don't need speakup
> and probably never will--is probably not going to gain results. If
> this is going to be done, it's going to be someone who needs speakup
> and has good kernel development skills, not some random kernel
> developer with nothing else to do. Things just don't work that way. I
> wish I could do it, but what I know about kernel hacking you could
> write on a 3 by 5 card in jumbo braille and still have blank space
> left over. <grin> Application programming is fine, but once I hit
> kernel land my head starts to hurt.
> 
> 
> On 03/02/2011 01:20 PM, Steve Holmes wrote:
> > Hi Jacob,
> >
> > I too use Arch Linux but also experience the same problem you do.
> > Though I didn't get into messing with kernel details, I tried the
> > solution that Chuck suggested in his previous message, but no joy
> > for me either. My failure to get serials to work goes back to
> > something like 2.6.34. 've been trying this with a Speakout, using
> > the speakup_spkout driver. I thought someone told me that driver
> > had a bug of some kind but I really would like to be able to use an
> > external synthesizer, especially if software speech goes south when
> > playing with pulse audio or other such evil things.
> >
> > I really wish we could get to the bottom of this serial problem
> > since that used to be speakup's life blood. I think many of us are
> > hoping the recent kernel integration might lead us to support in
> > getting the serial support beefed up so you could even use USB or
> > PCI serial ports and not be locked into the old ones which hardly
> > exist anymore on most new computers.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> 
> iQEcBAEBAgAGBQJNbrhSAAoJEDtK6CrF/Uo1VpoIAIacStbNQuDqqB6hViV3Pru8
> fgsXELuFB7Vt3FKXYREXumLWyHQq1GCRxAPIoQbyC5oQaFYPbFSgVVXa7NRNk1jZ
> MigBzAIqtiW5ZBUqwf1R/VtiJS9pYirXqgDj9ZbJkFrkSvSIpqujMNju77dfvOjI
> an2VWw3qNE7Ol8iN3ptBxRW6NZ+CEvf2itNi8QFZGB+16ba2OZGsiatYRRtGfHq4
> WBocSDf5QBuKIbBxUii9DrdiP50wlGAGiHB7A6RhtQaHYkPvdAaM9VyQqSRnTG7i
> 6kZ+H6TdyiAZkxPdMLE7DHWIXHeAWfRa1Gwy+GKLsc9h3a6RDuO9bbyeCla7cy0=
> =Jxjn
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> 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 [this message]
           ` Christopher Brannon
             ` Steve Holmes
         ` Christopher Moore
           ` Zachary Kline
             ` Albert Sten-Clanton
               ` 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=20110303161828.GA21823@lnx3 \
    --to=steve@holmesgrown.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).