public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Ling Su <lingsu@palmmicro.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>,
	eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Regarding to eCos on VRC4373
Date: Wed, 10 Jan 2001 15:45:00 -0000	[thread overview]
Message-ID: <20010110174919.A9657@visi.com> (raw)
In-Reply-To: <00b801c07b51$ca308a00$0201a8c0@raccoon>

On Wed, Jan 10, 2001 at 02:07:57PM -0800, Ling Su wrote:

> If I need a timer faster than 10ms/tick, could I increase denominator or
> decrease the numerator? I can it is a caculated value, user can not specify.
> How could I change them and what is the consequences?

The last time I messed with changing the tick value (10 or 11
months back) I discovered that there were several places
(tests, network stuff, IIRC) that assumed a 10ms tick.  It's
not a big problem, but something to be aware of.  I had a
system that seemed to work fine with a 1ms tick. I never
bothered to fix the network timings, since I decied to change
back to a 10ms tick.

-- 
Grant Edwards
grante@visi.com

      parent reply	other threads:[~2001-01-10 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 14:59 Ling Su
2001-01-09 16:44 ` Jonathan Larmour
2001-01-09 23:37   ` Ling Su
2001-01-10  3:30     ` Nick Garnett
2001-01-10  5:15       ` [ECOS] assertion checks for stack Joerg Rapka
2001-01-10  9:10     ` [ECOS] Regarding to eCos on VRC4373 Jonathan Larmour
2001-01-10  0:19   ` Ling Su
2001-01-10  9:08     ` Jonathan Larmour
     [not found]   ` <005e01c07ad5$5ba58210$0301a8c0@leopard>
2001-01-10  9:17     ` Jonathan Larmour
2001-01-10 14:08       ` Ling Su
2001-01-10 14:17         ` Jonathan Larmour
2001-01-10 15:45         ` Grant Edwards [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=20010110174919.A9657@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=lingsu@palmmicro.com \
    /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).