Skip to content
Snippets Groups Projects
  1. Feb 10, 2020
  2. Jan 15, 2020
  3. Jul 16, 2019
  4. May 26, 2019
  5. May 14, 2019
  6. Apr 30, 2019
  7. Apr 28, 2019
  8. Feb 12, 2019
  9. Jan 22, 2019
  10. Jan 07, 2019
    • Cédric Roux's avatar
      fix a lot of file mode · aea6b4b5
      Cédric Roux authored
      For whatever reason most of the files had their permission
      changed from 644 to 755, which is not wanted.
      aea6b4b5
  11. Oct 17, 2018
  12. Aug 24, 2018
  13. Jul 30, 2018
  14. Jul 22, 2018
  15. Jul 06, 2018
  16. Jun 28, 2018
  17. Jun 19, 2018
  18. Jun 01, 2018
  19. May 16, 2018
  20. May 13, 2018
  21. May 02, 2018
  22. Apr 25, 2018
  23. Apr 16, 2018
    • Bi-Ruei, Chiu's avatar
      Compare version number using MAKE_VERSION macro to provide better SW configuration: · 5c23af77
      Bi-Ruei, Chiu authored and Cédric Roux's avatar Cédric 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
  24. Apr 12, 2018
  25. Apr 09, 2018
  26. Apr 08, 2018
  27. Apr 06, 2018
    • Wang's avatar
      UE add RF board ZC706+AD9371 · 6f290e71
      Wang authored and Florian Kaltenberger's avatar Florian Kaltenberger committed
      Conflicts:
      	cmake_targets/build_oai
      	openair1/PHY/LTE_TRANSPORT/prach.c
      	openair1/SCHED/phy_procedures_lte_ue.c
      	targets/ARCH/COMMON/common_lib.h
      	targets/RT/USER/lte-softmodem.c
      6f290e71
  28. Mar 26, 2018
  29. Feb 05, 2018
  30. Jan 15, 2018
    • Cédric Roux's avatar
      import NFAPI work from David Price from Cisco (non-working commit, do not use it) · 7757b9e7
      Cédric Roux authored
      It has been chosen to not include the full history of commits
      from David. He included a binary version of wireshark, probably
      a modified one that understands NFAPI. Wireshark is released under
      the GPL license, we cannot include it in the repository. We could
      have done a next commit to remove this binary. But then it would
      still be present in the history of commits, which may not be allowed.
      And it would take space on disk. We could edit the history to remove
      wireshark entirely. But this operation is too complicated.
      
      There was also a pcap capture file, which has nothing to do in
      the history of commits and would take space on disk. There again,
      it's too difficult to edit the history to remove it.
      
      There was a file .gitignore that was also removed.
      
      The original history can be found on David's repository:
      https://gitlab.eurecom.fr/daveprice/openairinterface5g/
      The branch is: nfapi-ru-rau-split.
      
      A copy of that branch has been included in the internal OAI
      repository, for those who have access to it.
      The branch is the same. The last commit ID is
      91064382.
      
      You can compare the current commit with the commit 9106...
      to see what differs.
      
      The current commit has to be considered non-working.
      The commit following the current commit will fix problems with
      the work in the current commit.
      
      If you use git bisect, don't spend time analyzing the current
      commit.
      7757b9e7
  31. Jan 11, 2018
Loading