1. 04 Dec, 2017 1 commit
  2. 01 Dec, 2017 3 commits
  3. 20 Nov, 2017 7 commits
  4. 07 Nov, 2017 2 commits
  5. 05 Nov, 2017 1 commit
    • Fix next_table field width to handle MATCHLESS value (99) · 48bacb68
      Also, comments added to help identify conditionals, supporting
      debugging via the event logger.
      
      The next_table field was 4 bits, but init_program_state was
      assigning a value of '99' corresponding to matchless table type.
      When a modify_field tries to assign a value larger than the width
      of the target, bmv2 silently fails.
      
      Over in hp4-ctrl, t06 now works in its most essential test -
      a chain is created with simple_router -> firewall, and the
      router routes, and the firewall blocks/doesn't block correctly!
      David Hancock authored
  6. 03 Nov, 2017 1 commit
  7. 31 Oct, 2017 1 commit
  8. 30 Oct, 2017 2 commits
  9. 27 Oct, 2017 1 commit
  10. 26 Oct, 2017 1 commit
  11. 25 Oct, 2017 3 commits
  12. 24 Oct, 2017 2 commits
  13. 13 Oct, 2017 3 commits
  14. 12 Oct, 2017 1 commit
  15. 05 Oct, 2017 4 commits
  16. 26 Sep, 2017 1 commit
  17. 24 Sep, 2017 1 commit
  18. 22 Sep, 2017 1 commit
  19. 21 Sep, 2017 1 commit
  20. 17 Sep, 2017 1 commit
    • Modify drop.p4t - add vdev_ID match field to simplify controller · e91e38df
      Having the match field simplifies controller tasks related to
      composition management.  It has to do with handles associated
      with table entries.  Without the vdev_ID match field, essentially
      we have a tough time coordinating between vdevs that employ
      the drop primitive in the same stage/action (esp: two vdevs
      created from the same .p4).
      
      Also in this commit: hp4commands adds the startup rules that are
      required for proper functioning but independent of any vdev.
      David Hancock authored
  21. 12 Sep, 2017 1 commit
  22. 08 Sep, 2017 1 commit