From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andy Simpkins" To: Subject: RE: [ECOS] change of clock resolution Date: Tue, 24 Apr 2001 06:39:00 -0000 Message-id: References: <00c301c0ccb8$2ddc8790$1e00a8c0@OLENCZUK> X-SW-Source: 2001-04/msg00355.html 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 _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