From: "Andy Simpkins" <Andy.Simpkins@TardisMobile.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] change of clock resolution
Date: Tue, 24 Apr 2001 06:39:00 -0000 [thread overview]
Message-ID: <NEBBKCPHAKKLBOKILBONOEOHCBAA.Andy.Simpkins@TardisMobile.com> (raw)
In-Reply-To: <00c301c0ccb8$2ddc8790$1e00a8c0@OLENCZUK>
Someone shout out and correct me if I am wrong but the values you have
changed will have NO effect on the clock interval... if you have a timer
ticking at 100Hz it will remain ticking at 100Hz after you change these
values. what will have changed is eCos' perception of time (not the real
time).
If you want your clock ticks to be 10 times faster you need to change the
timer settings found in hal_clock_initialize <platform>_misc.c (or the
appropriate routine for your build)
Andy
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Michał Oleńczuk
Sent: 24 April 2001 13:15
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] change of clock resolution
I asked how to change real time clock resolution on PC i386 platform.
I received the answer with advice to change CYGNUM_HAL_RTC_PERIOD. I've
changed CYGNUM_HAL_RTC_PERIOD, CYGNUM_HAL_RTC_NUMERATOR and
CYGNUM_HAL_RTC_DENOMINATOR in "hal_i386_pc.h" to get larger resolution, but
it had no effect (100 ticks is still equal to 1sec). Is it possible that
clock resolution is "unchangeable" at PC platform?
What I'm doing wrong?
--
Michal Olenczuk
POLAND
mailto: olenczuk@rts.com.pl
tel. 0604091867
next prev parent reply other threads:[~2001-04-24 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 4:14 Micha&lstrok
2001-04-24 6:39 ` Andy Simpkins [this message]
2001-04-24 9:48 ` Jonathan Larmour
2001-04-25 1:11 ` Andy Simpkins
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=NEBBKCPHAKKLBOKILBONOEOHCBAA.Andy.Simpkins@TardisMobile.com \
--to=andy.simpkins@tardismobile.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).