From: "Andy Simpkins" <Andy.Simpkins@TardisMobile.com>
To: <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] change of clock resolution
Date: Wed, 25 Apr 2001 01:11:00 -0000 [thread overview]
Message-ID: <NEBBKCPHAKKLBOKILBONMEONCBAA.Andy.Simpkins@TardisMobile.com> (raw)
In-Reply-To: <3AE5AE45.ED8E219B@redhat.com>
thanks
-----Original Message-----
From: jlarmour@cambridge.redhat.com
[ mailto:jlarmour@cambridge.redhat.com]On Behalf Of Jonathan Larmour
Sent: 24 April 2001 17:48
To: Andy.Simpkins@TardisMobile.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] change of clock resolution
Andy Simpkins wrote:
>
> 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)
No the PERIOD is what is used to program the clock and is passed to
hal_clock_initialize by the kernel.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
prev parent reply other threads:[~2001-04-25 1:11 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
2001-04-24 9:48 ` Jonathan Larmour
2001-04-25 1:11 ` Andy Simpkins [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=NEBBKCPHAKKLBOKILBONMEONCBAA.Andy.Simpkins@TardisMobile.com \
--to=andy.simpkins@tardismobile.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).