• Davide Ciminaghi's avatar
    compliance: 11.2 c: take followup cf into account · c371afa5
    Davide Ciminaghi authored
    11.2 c says:
    
    If the twoStepFlag bit of the flagField of the of the Sync message is TRUE,
    indicating that a Follow_Up message will be received, then
    
            <offsetFromMaster> = <syncEventIngressTimestamp> -
           <preciseOriginTimestamp> - <meanPathDelay> -
           correctionField of Sync message -
           correctionField of Follow_Up message.
    
    Before this patch, only the correctionField of the Sync message was
    subtracted. We fix things by adding the Follow_Up correctionField to the
    Sync correctionField.
    
    Now m_to_s_dly as calculated in pp_servo_got_sync is:
    
    t2 - t1 - sync_cf - follow_up_cf
    c371afa5
Name
Last commit
Last update
arch-bare-i386 Loading commit data...
arch-bare-x86-64 Loading commit data...
arch-sim Loading commit data...
arch-unix Loading commit data...
arch-wrpc Loading commit data...
arch-wrs Loading commit data...
configs Loading commit data...
doc Loading commit data...
etc Loading commit data...
include/ppsi Loading commit data...
lib Loading commit data...
lib-bare Loading commit data...
pp_printf Loading commit data...
proto-ext-whiterabbit Loading commit data...
proto-standard Loading commit data...
scripts Loading commit data...
time-bare Loading commit data...
time-sim Loading commit data...
time-unix Loading commit data...
time-wrpc Loading commit data...
time-wrs Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
COPYING.LIB Loading commit data...
Kconfig Loading commit data...
MAKEALL Loading commit data...
Makefile Loading commit data...
Makefile.kconfig Loading commit data...
diag.c Loading commit data...
fsm.c Loading commit data...
timeout.c Loading commit data...