1. 07 Jul, 2013 1 commit
  2. 12 Jun, 2013 6 commits
  3. 08 Jun, 2013 4 commits
  4. 05 Jun, 2013 23 commits
  5. 29 May, 2013 2 commits
  6. 23 May, 2013 4 commits
    • Alessandro Rubini's avatar
      time-wrpc: new directory · 97c0c129
      Alessandro Rubini authored
      This includes the time (and net) operations from arch-wrpc. Like bare,
      arch-wrpc is not able to use a different timing engine than its own.
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      97c0c129
    • Alessandro Rubini's avatar
      time-bare: new directory · 5c23eca2
      Alessandro Rubini authored
      This commit separates to its own directory the timing code specific
      to bere linux implementations.  If you build with ARCH=bare-i386
      or ARCH=bare-i386-64, TIME=bare is automatically selected.
      
      Please note how bare builds don't allow externally-set TIME=, as the
      architecture Makefile forces "TIME := bare" (not "TIME ?= bare").
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      5c23eca2
    • Alessandro Rubini's avatar
      time-unix: new directory, selected by arch-unix · b6eb1385
      Alessandro Rubini authored
      This is the first implementation of the concept ot "TIME=" on the
      configuration of ppsi.  Time-related code that used to live in arch-unix
      is now split into its own directory. If you have special timing hardware,
      you can write your own pp_network_operations and pp_time_operations
      in your own directory and select them using TIME= .
      
      We'll do Linux-specific hardware timestamping soon, and WhiteRabbit as
      well.
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      b6eb1385
    • Alessandro Rubini's avatar
      ppsi.h: declare unix_time_ops and unix_net_ops for everyone · 7909e33c
      Alessandro Rubini authored
      The unix time and network operations are going to be used as a fall-back
      solution by other timing engines.
      
      For example, hardware-specific timestamping capabilities can be
      selected (such as the Linux ioctl API) but if the Ethernet interface
      (and thus the pp_instance) doesn't support the feature, related code
      will be able to set back the unix operations in place.
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      7909e33c