This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: # ticks per second?


On Wed, Aug 30, 2000 at 06:41:35PM +0100, Hugo 'NOx' Tyson wrote:

> And there is a C++ solution to this within the kernel.  See the test
> clockcnv.cxx in the kernel tests directory for how to use it, and clock.cxx
> in the kernel source for its implementation.
[...]
> thus making it all far less likely to underflow or lose precision.
> 
> It doesn't (yet) have a KAPI (C) API.  It's used within the uITRON
> implementation to get milliSecond clocks, which is bare C++.
> 
> Feel free to design and contribute a KAPI API?

Since it's not possible to change the clock tick period at
run-time (right?), I'd try for a pre-processor constant.  But
that might be pretty hard to do in an accurate, general way.

-- 
Grant Edwards
grante@visi.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]