Thanks! That applied perfectly and I just pushed it.
Hopefully it corrected the anomalies you saw. FWIW I just noticed the Pi clock driver does not have support for getting the nanoseconds since the last tick so timestamps will have the granularity of the clock tick. On 7/7/2015 3:52 PM, Jan Sommer wrote:
Hi, I hope that's how this works. Here is a patch for the raspberrypi clock driver to use the correct value for the timer counter based on rtems_configuration_get_microseconds_per_tick() as discussed in the user-list. Cheers, Jan -------------------------------------------------------------
-- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel