Re: Any leap year issues caused by Ada yesterday?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Tue, 06 Mar 2012 17:59:04 +0000, Simon Wright wrote:

> The timebase ran off the same crystal as the decrementer, so all were
> internally sync'd. Internally, our synchronised time was
> (Ada.Calendar.Clock (at last clock interrupt, of course) + high-res time
> since last clock interrupt).

You could improve that a bit by putting Ada.Calendar.Clock into a loop.
When it returns a different value, you exit the loop and take that value
for the time base.

If the quartz is same you need not to synchronize it anymore. Since the
multiplier is known you simply add the RTC minus its value at the base
multiplied by the factor and converted to Duration (or Time_Span) to the
base and use that instead of the original Ada's Clock.

Did you check the kernel settings? It has a variable that sets the time
source to the RTC. This might work on your PPC's BSP. The effect is that
the system clock is changed each time when queried rather than upon timer
interrupts.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de