public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Lidsten" <Daniel.Lidsten@combitechsystems.com>
To: "eCos Discussion" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Change system tick during runtime
Date: Wed, 01 Oct 2003 12:55:00 -0000	[thread overview]
Message-ID: <004B1D7A5257174C9044A1B7BD0E60EDDAE739@ratatosk.combitechsystems.com> (raw)

Hi,

Is there any way of changing the system tick during runtime? I have made
a quick test by letting an application provided variable be used when
setting the decrementer in the HAL_CLOCK_*-functions. This will make the
system generate tick more or less often depending on the value set.
However, the drawback is that the system expects that we have a
heartbeat of 100Hz and that will differ when changing the decrementer.
Is there any way to get around this? Is there any way to change the
CYGNUM_HAL_RTC_DENOMINATOR during runtime so that the change will affect
every file that use it? I want to be able to have 10000 ticks per second
but then i also need to let the system know that we have 10000 ticks per
seconds so that not all timeouts and stuff gets all confused.

Regards, Daniel Lidsten

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-10-01 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 12:55 Daniel Lidsten [this message]
2003-10-01 12:59 ` Slawek
2003-10-01 13:03 ` Gary Thomas
2004-01-28  8:53   ` [ECOS] Changing CPU clock frequency on the fly Gratian Crisan
2004-01-28 15:58     ` Bart Veer
2003-10-01 13:16 [ECOS] Change system tick during runtime Daniel Lidsten
2003-10-01 13:31 ` Gary Thomas
2003-10-01 17:06 ` Nick Garnett

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=004B1D7A5257174C9044A1B7BD0E60EDDAE739@ratatosk.combitechsystems.com \
    --to=daniel.lidsten@combitechsystems.com \
    --cc=ecos-discuss@sources.redhat.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).