Steve Deiters wrote: >>> Hi, >>> >>> We had a similar problem. We solved it by compiling the >> native skin as >>> a module and loading it _after_ the kernel has been >> syncronized with >>> the real-time clock chip. >> Yes, that works too. There is also an option in the kernel >> for the kernel to synchronize with the RTC clock directly, >> without requiring hwclock. I do not know if it is run before >> starting Xenomai though. > > I have a similar requirement, except I want to keep the Xenomai clock > synchronized with Linux services that use adjtime/adjtimex, e.g. NTP. > It is not sufficient in this case to delay the startup of Xenomai. I > suppose as a workaround I could create a low priority periodic thread > that reads the Linux clock with gettimeofday and sets the Xenomai one > with clock_settime.
Periodically setting the time is risky if timed jobs depend on Xenomai's real-time clock - it may jump in all directions... > > Any other suggestions for providing timestamps to real time tasks in > this case? Do you just need precise timestamps from with real-time tasks, or do you have to synchronize timer events of the Xenomai core on an external clock? For the former case (precisely our scenario), we laid the ground to extend Xenomai 2.5 with RT-safe syscalls to obtain Linux's view on gettimeofday. It "just" needs some polishing to post this for upstream. Wolfgang (CC'ed) is working on this. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
