1. 23 Jun, 2017 1 commit
  2. 12 Jun, 2017 1 commit
    • Alessandro Rubini's avatar
      pdelay: rework and extend prev commit · 31f08f19
      Alessandro Rubini authored
      The previous commit is not enough as a fix.  This may happen:
      
          - we invalidate stamps after processing them
          - we send request
          - get reply, loose reply-fup
          - send request
          - loose reply, get f-up
      
      So we now invalidate when sending the request. And invalidate t4 alone
      as the beautifulness and symmetry of the previous commit is lost
      anyways.
      
      Note: there no need to invalidate stamps in e2e mode, because checking
      the sequence number to validate RX frames is enough.  But here all
      replies match the sequence number, so the problem is not caught and
      stamps from different tuples are mixed.
      
      Example beofre this commit, with trimmed stamps (was 1497283863):
      
         diag-frames-1-wr1: SENT 54 bytes at 863.333173928 (pdelay_req)
         diag-frames-1-wr1: RECV 54 bytes at 863.334158796 (type 3, pdelay_resp)
         diag-frames-1-wr1: Drop received frame
         diag-frames-1-wr1: SENT 54 bytes at 864.479336104 (pdelay_req)
         diag-frames-1-wr1: Drop received frame
         diag-frames-1-wr1: RECV 54 bytes at 864.481095164 (type a, presp_follow_up)
      
         diag-servo-2-wr1: servo:t3 = 864:479336104:0
         diag-servo-2-wr1: servo:t4 = 863:333174267:586
         diag-servo-2-wr1: servo:t5 = 864:480295312:0
         diag-servo-2-wr1: servo:t6 = 863:334158796:773
         diag-servo-2-wr1: ->mdelay = -2:-292298352:359
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      31f08f19
  3. 03 Mar, 2017 2 commits
  4. 01 Mar, 2017 3 commits
  5. 31 Jan, 2017 1 commit
  6. 21 Nov, 2016 1 commit
  7. 04 Nov, 2016 6 commits
  8. 25 Oct, 2016 3 commits
  9. 20 Sep, 2016 8 commits
  10. 16 Jun, 2016 1 commit
  11. 16 May, 2016 5 commits
  12. 13 Mar, 2015 1 commit
  13. 13 Nov, 2014 4 commits
  14. 07 Nov, 2014 1 commit
  15. 06 Nov, 2013 1 commit
    • Alessandro Rubini's avatar
      bug workaround for slave states: don't refuse a new master · 577ed159
      Alessandro Rubini authored
      This works around a design problem that must be checked carefully.
      The "is from current parent" flags set at receive time reveales bad,
      as we should only check when needed.
      
      So by now just say it is the current parent if we don't have a current
      parent yet (i.e., we are not in error, even if it is not from current
      parent).
      
      Also, forget about current parent and foreign masters when the servo
      is initialized (e.g., at link-up on the wr node).
      Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
      577ed159
  16. 24 Sep, 2013 1 commit