- 20 Sep, 2016 32 commits
-
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
See Table 13. Note that we keep currentUtcOffset as it is and reset currentUtcOffsetValid, because we presently don't know about leap seconds. leap59 and leap61 are forced to zero.
-
Davide Ciminaghi authored
See Table 13.
-
Davide Ciminaghi authored
See Table 20.
-
Davide Ciminaghi authored
We don't support alternate masters at present.
-
Davide Ciminaghi authored
We're not a transparent clock, so this should be ok.
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
We also avoid setting the same flag while handling a Pdelay_Resp_Followup.
-
Davide Ciminaghi authored
remove duplication, remove code size
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
11.3 d says: Upon receipt of the Delay_Resp message by the slave: 1) If the received Sync message indicated that a Follow_Up message will not be received, the <meanPathDelay> shall be computed as: <meanPathDelay> = [(t2 - t3) + (receiveTimestamp of Delay_Resp message - originTimestamp of Sync message) - correctionField of Sync message - correctionField of Delay_Resp message]/2. 2) If the received Sync message indicated that a Follow_Up message will be received, the <meanPathDelay> shall be computed as: <meanPathDelay> = [(t2 - t3) + (receiveTimestamp of Delay_Resp message - preciseOriginTimestamp of Follow_Up message) - correctionField of Sync message - correctionField of Follow_Up message - correctionField of Delay_Resp message]/2. We assume that: t1 = originTimestamp of Sync message (one step) or t1 = preciseOriginTimestamp of Follow_Up message (two steps) and t4 = receiveTimestamp of Delay_Resp message wich is true for masters not supporting sub-nanosecond timestamps (we don't support sub-ns precision via standard protocol, so the assumption should be true for us). As sync (or followup) arrives, we calculate m_to_s_dly, which is: t2 - t1 - cf_sync - cf_followup When delay_resp arrives, we calculate s_to_m_dly, which is: t4 - t3 - cf_delay_resp So [(m_to_s_dly + s_to_m_dly) / 2] should be equal to: (t2 - t3 + t4 - t1 - cf_sync - cf_followup - cf_delay_resp) / 2 which looks like the 11.3 d expression for mean path delay (note that cf_followup is zero for a one-step master). To get this result, we just save the delay_resp cf to ppi->cField.
-
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
-
Davide Ciminaghi authored
-
Davide Ciminaghi authored
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>
-
Alessandro Rubini authored
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>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
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>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Adam Wujek authored
remove rules like: --allmodconfig --kvmconfig --xenconfig --tinyconfig change directory with configs Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
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>
-
Adam Wujek authored
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>
-
- 14 Sep, 2016 4 commits
-
-
Adam Wujek authored
Uplift shmem from wr-switch-sw repo. Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
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>
-
Adam Wujek authored
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>
-
Adam Wujek authored
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>
-
- 25 Aug, 2016 1 commit
-
-
Adam Wujek authored
add util.c for functions get_monotonic_* Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 22 Aug, 2016 1 commit
-
-
Adam Wujek authored
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>
-
- 16 Aug, 2016 2 commits
-
-
Adam Wujek authored
shmem is locked already in the function wr_servo_update Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Alessandro Rubini authored
-