This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: change of clock resolution
- To: <jlarmour at redhat dot com>
- Subject: RE: [ECOS] change of clock resolution
- From: "Andy Simpkins" <Andy dot Simpkins at TardisMobile dot com>
- Date: Wed, 25 Apr 2001 09:06:15 +0100
- Cc: <ecos-discuss at sources dot redhat dot com>
- Reply-To: Andy dot Simpkins at TardisMobile dot 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