Rodrigo Rosenfeld Rosas wrote:
Philippe Gerum wrote:
Given the description above, just that some skin might return either
nucleus ticks or corrected timestamps to the applications, which would
in turn do some arithmetics for converting values they got from the skin
between both scales internally, and mistakenly use the result while
assuming that both scales are always in sync. In this situation, and
during a fraction of the time (i.e. the jitter), both scales might not
be in sync, and the result would be unusable.
But I still can't find a real situation where the user would need these values
to be in sync...
It's not a matter of dealing with users always doing The Right Thing,
but preferably preventing people from doing the wrong one.
Xenomai-core mailing list