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

Before this commit, ANNOUNCE messages were sent with grandmaster-related
fields equal to 0. Values for such fields were taken from the parentDS data
set, which did not look properly initialized.

Paragraphs 8.2.3.2 to 8.2.3.9 of the ieee1588 standard specify
initialization values for the parentDS data set.
Many such values come from the defaultDS, so care must be taken to
initialize the parent data set __after__ the default data set.
We do this in pp-initializing().
Signed-off-by: Davide Ciminaghi <ciminaghi@gnudd.com>

Please note that timeout_init is not resetting timeouts, it's just
saving the values for later settings.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The bmc may turn a port to passive state, so we need the
state in our state table.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

remove rules like:
--allmodconfig
--kvmconfig
--xenconfig
--tinyconfig

change directory with configs
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Now it is also possible to use for dot-config configuration:
make nconfig
make xconfig
make gconfig
make menuconfig

kconfig is taken from the linux kernel repo commit v4.8-rc1-19-g81abf25:
e50bd235 Merge tag 'lkdtm-v4.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linuxSigned-off-by: Adam Wujek <adam.wujek@cern.ch>

Fix command make config. The error was probably introduced by commit:
b88106b3 trivial: Makefile: fix for make v4
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Uplift shmem from wr-switch-sw repo.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Commit based on the commit from wrs-switch-sw repo described below. It does
not have impact on PPSI, just for consistency.

userspace/libwr: check shmem consistency in wrs_shm_get_and_check

Check the consistency of shmem during opening with wrs_shm_get_and_check.
It was possible that sequence number was increased during the opening, but it
was interpreted as version error.

Add defines describing different return errors.

This change is backward compatible.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Commit based on the commit from wrs-switch-sw described below.

userspace/libwr: improve locking of shmem

Keep explicitly lock bit in the sequence variable as a LSB bit.
This solution is backward compatible. The difference is only when shmem is
lock twice. Before it was treated as unlocked, now still as a lock.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Commit based on the commit mentioned below from wr-switch-sw repo.
It required to add a header wrs-msg.h to support "pr_error" function.
"pr_error" will be printed as regular error, all other pr_* are ignored.

userspace/libwr: Print error message on multiple shmem locks

Print error message when shmem is locked or unlocked multiple times.
To be precise it will print error only on even locks or unlocks.

Move the increment of sequence before checking the flags to simplify further
if-conditions.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

add util.c for functions get_monotonic_*
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Because picos_mu_prev was not updated in the correct place, variable
n_err_delta_rtt was increased at every update. This resulted in errors
on the switch via SNMP.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

shmem is locked already in the function wr_servo_update
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Increase of WRS_PPSI_SHMEM_VERSION is needed at least due to the commit:
pdelay/wrservo: wr_servo calculates link delay and offset to master using P2P
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Merge commits needed due to changes in the switch:
--uplift of the buildroot
--change names of the interfaces from wrX (0-17) to wriX (1-18)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We just reinit timeouts on reception of a delay response This way the
delay request interval is reinitialized and set to the proper value.

previous code failed for logSyncInterval < 0
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This fixes a bug introduced by f1d048c3
(conf.c: use f_simple_int() for assigning simple integer options):
we used ASSIGN_INT_FIELD for assigning values to variables shorter than
int, while the destination pointer was set to int *, so neighbouring
fields were overwritten.

Another commit in a non-merged branch adds a build-time check to
avoid repeating this bug, but field names changed, so let's avoid
cherry-picking it here at this point.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Before this commit, ANNOUNCE messages were sent with grandmaster-related
fields equal to 0. Values for such fields were taken from the parentDS data
set, which did not look properly initialized.

Paragraphs 8.2.3.2 to 8.2.3.9 of the ieee1588 standard specify
initialization values for the parentDS data set.
Many such values come from the defaultDS, so care must be taken to
initialize the parent data set __after__ the default data set.
We do this in pp-initializing().
Signed-off-by: Davide Ciminaghi <ciminaghi@gnudd.com>

This kills the ambiguously-named pp_ms_to_timeout(), and
adds pp_next_delay_{1,2,3}.

This commit meanwhile fixes the timeouts in the pdelay master (who didn't
consider the request timeout), and in the pdelay listener (because
LISTEN mode must send pdelay requests).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>