1. 24 Feb, 2020 1 commit
  2. 03 Feb, 2020 1 commit
  3. 13 Dec, 2019 1 commit
  4. 11 Oct, 2019 1 commit
  5. 14 Aug, 2019 1 commit
    • Jean-Claude BAU's avatar
      Fix PPS missing issue · ec89448c
      Jean-Claude BAU authored
      After around 36 hours, one PPS was missing. This was due to an issue in
      the WR extension. When the sequence id in the announce message was
      moving from 65535 to 0, the WR handshake was restarted. As a result of
      that, the side effects would be :
      - a missing PPS
      - an unlock of the PLL
  6. 02 Aug, 2019 1 commit
  7. 04 Jun, 2019 1 commit
    • Jean-Claude BAU's avatar
      Improve behavior when link up->down->up not detected. · 420da467
      Jean-Claude BAU authored
      When the link state changes rapidly, it can't be detected by PPSi. This
      is the case with the BTrain configuration. So we must detect that the
      peer has changed and restart the servo for a slave and use the right
      protocol (extension/ptp).
  8. 27 May, 2019 1 commit
    • Jean-Claude BAU's avatar
      [Issue:#196] WR time not set properly in GM mode · 36accb7e
      Jean-Claude BAU authored
      The WR time is set in GM mode as follow :
      1/ At startup the NTP time is set using wr_date script
      2/ PPSi calls the tool wr_date with parameters "set host". It will be
      called every time it detects a PLL transition from UNLOCKED to LOCKED
      state. Also PPSi provide a error counter 'gmUnlockErr' which gives the
      number of time the PLL unlocked.
      3/ Parameters "-v set host" in wr_date tool, set only the second part of
      the WR time. The time is set in a middle of two WR seconds ticks.
  9. 24 May, 2019 1 commit
  10. 14 May, 2019 1 commit
  11. 02 May, 2019 1 commit
  12. 10 Apr, 2019 1 commit
  13. 09 Apr, 2019 1 commit
    • baujc's avatar
      Review of WR protocol implementation · 0b031b22
      baujc authored
      - It has now its own state table
      - The servo is shared with L1Sync extension. It means that servo
      calculation is now following the new standard IEEE 1588
      - It stay compatible with older versions of the switch. The correction
      field value in the exchange messages are still not compliant with the
      standard to keep the compatibility.