1. 26 Jun, 2019 2 commits
    • Jean-Claude BAU's avatar
      [New feature] Check for incoming leap second · 24ea4b97
      Jean-Claude BAU authored
      - Add a new tool (wrs_leapsec) to check for an incoming leap second. It
      is done by parsing the leap second file. If a leap second is detected
      then adjustment parameters for the clock algoritm are set in the kernel.
      - Start the tool at startup
      - With cron, execute the tool every 3 hours
      - As many tools need to parse the leap seconds file, functions have been
      added in the library and then called by these tools
      24ea4b97
    • Jean-Claude BAU's avatar
      wr_date.c: Add option · 6f18a2ac
      Jean-Claude BAU authored
      The -n option in the wr_date tool is used for a dry run. It execute the
      code without applying changes in the system and the hardware.
      However calling "wr_date -n set host" was not setting the date but
      applying the TAI offset. To make things more consistant, a new option
      has been added. Calling "wr_date set host tai" now sets only the TAI
      offset.
      The wr_date script has been changed to take into account this
      modification of the behavior.
      6f18a2ac
  2. 03 Jun, 2019 2 commits
    • Jean-Claude BAU's avatar
      [Issue:#196] WR time not set properly in GM mode · f7c33411
      Jean-Claude BAU authored
      1/ wr_date script:
      - Started before PPSi
      - Set number of NTP retries to 10 if GM otherwise 1. GM info is
      extracted from dot-config
      - Clock source is controlled directly with wr_date tool
      - Can be started any time without any risk to set a wrong date (see
      point 2)
      2/ wr_date
      - 'set host' parameters take into account the time mode ( FR: set
      sec+ns, BC: time cannot be set, GM: set seconds only+wait to be in a
      middle of a second)
      - function substrat_substrat() moved to time_lib.h. Also used by wr_mon
      3/ wr_mon
      - Print TAI-UTC
      - Update Timing Mode & PLL locking state displayed values
      f7c33411
    • Benoit Rat's avatar
  3. 10 Apr, 2019 2 commits
  4. 21 Sep, 2018 1 commit
  5. 10 Aug, 2018 1 commit
  6. 01 Dec, 2016 1 commit
  7. 11 Aug, 2016 2 commits
  8. 05 Apr, 2016 2 commits
  9. 01 Apr, 2016 1 commit
  10. 22 Jul, 2015 1 commit
  11. 15 Jul, 2015 1 commit
  12. 10 Jul, 2015 1 commit
  13. 09 Jul, 2015 1 commit
  14. 29 Jun, 2015 1 commit
  15. 16 Jan, 2015 1 commit
  16. 04 Jan, 2015 2 commits
  17. 10 Dec, 2014 1 commit
  18. 05 Dec, 2014 2 commits
  19. 04 Dec, 2014 1 commit
  20. 28 Nov, 2014 5 commits
  21. 20 Nov, 2014 1 commit
  22. 19 Nov, 2014 1 commit
  23. 17 Oct, 2014 1 commit
  24. 16 Oct, 2014 1 commit
    • Alessandro Rubini's avatar
      boot procedure: use non-blocking write to /dev/ttyGS0 · 16d93070
      Alessandro Rubini authored
      If the usb cable is disconnected, any write to /dev/ttyGS0 goes to a
      buffer until it fills. Then, any further write will block. This means
      the messages towards the user ("uncompressing filesystem... done" etc)
      caused the update procedure to stop.
      
      This fixes the problem by using non-blocking write for the messages:
      if nobody`s reading the messages are just discarded by the kernel.
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      16d93070
  25. 30 Sep, 2014 1 commit
  26. 24 Sep, 2014 2 commits
  27. 04 Sep, 2014 1 commit
  28. 29 Jul, 2014 1 commit