From: Charles Crawford <ccrawford@Starpower.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Help! The Dectalk PC is hosing my clock!
Date: Mon, 3 May 2004 05:18:53 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0405030514460.10554-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0405021542520.18111@homerun.midsouth.rr.com>
I wish I could remember my Jiffy_Delta and delay settings but I think
they were the default settings. I do remember a bit of trouble in
getting the dec pc to shut up with the control key but nothing serious.
As was suggested by a message from someone else, I don't understand why
you would have the problem you are having. The only thing about which I
can speculate is perhaps a hardware interupt issue?
On Sun, 2 May 2004,
Adam Myrow wrote:
> I'm using kernel 2.4.26 under Slackware 9.1 if that helps. Just to verify
> that it is indeed the Dectalk, I turned off speech and used Brltty only to
> read several emails, while repeating the same loop on another console of
> comparing the date with the system clock. It stayed stable. As soon as I
> started up the Dectalk speaking again, it started wondering again. When I
> started typing this message, it was within a few milliseconds, and is now
> over 4 seconds off. Since you were using it under Redhat, I'm wondering
> if the Dectalk driver is tuned for Redhat's faster clock rate? I recall
> when Redhat 8 came out, they tweaked a value having to do with the clock
> speed of the kernel or something, and a lot of people had to adjust
> jiffy_delta and delay_time in Speakup to compensate because it caused
> their synthesizers to be choppy. I'm wondering if adjusting those values
> might help? My jiffy_delta is 50, and my delay_time is 500 now, which are
> default values.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
-- Charlie Crawford
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` shaun Oliver
` Hart Larry
` Adam Myrow
` Charles Crawford
` Adam Myrow
` Charles Crawford [this message]
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=Pine.LNX.4.44.0405030514460.10554-100000@localhost.localdomain \
--to=ccrawford@starpower.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).