From: Bue Vester-Andersen <listadr1@dkblind.dk>
To: "'speakup@braille.uwo.ca'" <speakup@braille.uwo.ca>
Subject: RE: Fragmented speech with speakup and apollo
Date: Fri, 14 Feb 2003 13:31:04 +0100 [thread overview]
Message-ID: <AC6FA4286BC8D511BE7200008369C2B01FA7FB@MAIL01> (raw)
Hi Kirk,
Thanks for the help. I am using Speakup out of the Red hat 8.0 box. The
options you mentionare they in the kernel or in speakup? where can I change
them?
Regards
Bue
-----Original Message-----
From: Kirk Reiser [mailto:kirk@braille.uwo.ca]
Sent: Friday, February 14, 2003 12:34
To: speakup@braille.uwo.ca
Subject: Re: Fragmented speech with speakup and apollo
Hi Bue: That can happen from a couple of situations. I am not sure
about the ins-and-outs of Redhat 8.0 because Bill Acker takes care of
our Redhat distribution. I suspect he'll have something to say on
your problem as well. Are you using a speakup redhat kernel out of
the box? In later kernels you can see the behaviour you're indicating
because of a processor greater than a 686 of some ilk. If that
happens to be the problem and I'm not convinced it is you can get
around it by adjusting delay_time and jiffy_delta. The defaults for
those values at the standard 100hz interrupt frequency is
delay_time=500 and jiffy_delta=5. If you are running 1000hz jiffies
then you need to increase jiffy_delta=50.
Good luck and let us know.
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Bue Vester-Andersen [this message]
` Kirk Reiser
-- strict thread matches above, loose matches on Subject: below --
Bue Vester-Andersen
` Kirk Reiser
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=AC6FA4286BC8D511BE7200008369C2B01FA7FB@MAIL01 \
--to=listadr1@dkblind.dk \
--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).