1. 29 May, 2018 1 commit
  2. 24 May, 2018 1 commit
  3. 09 May, 2018 1 commit
    • Cedric Roux's avatar
      import work from the branch nfapi-L2-emulator to merge it to develop · f254107b
      Cedric Roux authored
      It was not possible to merge the branch directly, because the
      history of this branch contains files that cannot be in the
      repository, namely wireshark from Cisco work on nFAPI.
      
      As for Cisco work on nFAPI, a special commit containing all the
      work is thus created.
      
      Below is the output of the command:
      git log --graph 184d51c6..61276d87
      
      184d51c6 is the commit ID of the develop
      branch prior to the merge.
      
      61276d87 is the commit ID of the
      nfapi-L2-emulator branch prior to the merge.
      
      The commit 61276d87 (and all its
      history) will be removed from the main OAI repository. It is
      present in the internal OAI repository for those who have access
      to it.
      
      There was also some cleanup done on the code.
      
      Some changes were necessary to have the eNB functional. They may have an
      impact on the FAPI ...
      f254107b
  4. 29 Apr, 2018 1 commit
  5. 22 Apr, 2018 1 commit
  6. 16 Apr, 2018 1 commit
    • Bi-Ruei, Chiu's avatar
      Compare version number using MAKE_VERSION macro to provide better SW configuration: · 5c23af77
      Bi-Ruei, Chiu authored and Cedric Roux's avatar Cedric Roux committed
      1. Previous SW configuration for different RRC version relies on whether macro Rel10,
         Rel14 defined or not by checking #ifdef Rel14 or #if defined(Rel10) || defined(R14).
         Whenever there is a newer RRC version, e.g. Rel15, it will be very a tedious and
         error-prone job to add defined(Rel15) in every place.
      
      2. Some RRC messages are defined in release 13 instead of release 14, NB-IoT
         feature is one of such example. Our code shall reflect this fact instead of using
         an afterward version number in software configuration.
      
      3. Some RRC messages or some fields of certain RRC messages are added in the middle
         a release, e.g. SystemInformationBlockType1_v1310_IEs_t defined in RRC 13.1.0
         and RRC 9.2.0 made some changes to SIB12 and SIB13 so we have sib12_v920 and
         sib13_v920 fields in SIB12 and SIB13's struct.
         We need a finer grain of control when using ASN1 from different RRC version.
      
      4. S1AP also has this problem that it use UPDATE_RELEASE_9 and UPDATE_RELEASE_10 to
         differentiate between various S1AP version.
      
      This commit propose using MAKE_VERSION(x,y,z) to designate the version number and
      modify current conditional compilation accordingly.
      
      Note: 2018/04/16, Modified based on Cedric's comment.
      5c23af77
  7. 09 Apr, 2018 1 commit
  8. 23 Mar, 2018 1 commit
  9. 22 Mar, 2018 3 commits
  10. 14 Mar, 2018 1 commit
  11. 09 Mar, 2018 1 commit
  12. 08 Mar, 2018 2 commits
  13. 02 Mar, 2018 2 commits
  14. 01 Mar, 2018 1 commit
  15. 22 Feb, 2018 3 commits
  16. 20 Feb, 2018 1 commit
  17. 15 Feb, 2018 1 commit
  18. 14 Feb, 2018 1 commit
  19. 13 Feb, 2018 5 commits
  20. 12 Feb, 2018 3 commits
  21. 31 Jan, 2018 8 commits