1. 14 Oct, 2013 1 commit
  2. 11 Oct, 2013 9 commits
  3. 10 Oct, 2013 2 commits
  4. 01 Oct, 2013 1 commit
  5. 26 Sep, 2013 1 commit
  6. 24 Sep, 2013 7 commits
  7. 23 Sep, 2013 1 commit
  8. 20 Sep, 2013 3 commits
  9. 10 Sep, 2013 1 commit
  10. 26 Aug, 2013 1 commit
  11. 16 Aug, 2013 1 commit
  12. 05 Aug, 2013 2 commits
  13. 30 Jul, 2013 3 commits
  14. 26 Jul, 2013 2 commits
    • Grzegorz Daniluk's avatar
      add new commands for setting time · 29f1b100
      Grzegorz Daniluk authored
      When WR PTP Core is set in GrandMaster mode it aligns its nanosecond
      counter to 1-PPS and 10MHz coming from external source. When user wants
      to set seconds counter to a desired value (with _time set_ command), the
      nanosecond counter was also set (zeroed) causing additional (random)
      offset to the external source. The commit adds _time setsec_ and _time
      setnsec_ for setting only seconds or nanoseconds counter without
      affecting the other one. Now, when user wants to set current time on a
      GrandMaster Node he has to call _time setsec_ command after _mode gm_
      29f1b100
    • Grzegorz Daniluk's avatar
      remove Tom-dependent code · e3b8dbc4
      Grzegorz Daniluk authored
      e3b8dbc4
  15. 25 Jul, 2013 3 commits
  16. 05 Jul, 2013 1 commit
  17. 23 May, 2013 1 commit
    • Alessandro Rubini's avatar
      check-error: new file, to catch undesired function calls · 92b23022
      Alessandro Rubini authored
      We don't want to call the real printf, which brings in the whole of
      newlib, but it sometimes happen. So let's diagnose the problem
      immediately rather than letting users wonder what is wrong with the
      size.
      
      Similarly, if building under ppsi, ensure we are not calling libgcc
      division functions: any 64-bit division my be done with __div64_32
      offered by ppsi/lib (copied from the kernel).
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      92b23022