Skip to content
Snippets Groups Projects
  1. May 16, 2018
  2. Apr 29, 2018
  3. Apr 25, 2018
  4. Apr 22, 2018
  5. Apr 13, 2018
  6. Apr 09, 2018
  7. Apr 08, 2018
  8. Apr 06, 2018
    • Raymond Knopp's avatar
      warning remove · eee76738
      Raymond Knopp authored
      eee76738
    • root's avatar
      UE add RF board ZC706+AD9371 · 6f290e71
      root authored
      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
  9. Apr 05, 2018
  10. Mar 20, 2018
  11. Mar 16, 2018
  12. Mar 15, 2018
  13. Mar 09, 2018
  14. Mar 08, 2018
  15. Feb 23, 2018
  16. Feb 22, 2018
    • Cedric Roux's avatar
      remove compilation warnings · 365ca71a
      Cedric Roux authored
      365ca71a
    • Cedric Roux's avatar
      integration: cleanup · 8ca5fb4e
      Cedric Roux authored
      - remove spaces at the end of lines
      - remove useless dead code
        use: git show -p <this commit> -w
        to see it clearly
      8ca5fb4e
    • Cedric Roux's avatar
      integration fix: fix crash · 58eab751
      Cedric Roux authored
      With value 4 when connecting one UE and doing some downlink
      iperf TCP there is a crash. Probably due to the multiple wrong
      RA detected leading to uplink failure of fake UE that never
      sends Msg3 (because, well, there is no other UE).
      
      This is another problem that will be fixed at some point.
      
      Anyway, this value 4 fails. Let's put back 3.
      58eab751
  17. Feb 20, 2018
  18. Feb 19, 2018
  19. Feb 17, 2018
  20. Feb 16, 2018
  21. Feb 14, 2018
    • Cedric Roux's avatar
      fixup previous bad merge (UE disconnection did not work properly anymore) · 91332d39
      Cedric Roux authored
      Doing airplane mode off to connect a cots UE followed by airplane mode on
      to disconnect it gives very bad results (bad disconnection with lots of
      UL failures followed by lots of logs in the eNB). It used to work properly
      after the work done by Xu Bo.
      
      It turns out that in 2018.w04 things were still working okay. But
      in 2018.w05 no.
      
      So I ran:
      
          git diff 2018.w04 2018.w05
      
      And I checked all the modifications that I thought were relevant
      (everything related to the UE, oaisim, if4 and fapi has not been checked).
      
      This commits takes back the version of 2018.w04.
      
      The modifications in openair2/RRC/LITE/rrc_eNB.c are necessary, I think.
      
      The other modifications may not be necessary or even wrong. To be checked
      at some point.
      91332d39
  22. Feb 13, 2018
  23. Feb 05, 2018
  24. Jan 28, 2018
  25. Jan 26, 2018
  26. Jan 22, 2018
  27. Jan 21, 2018
  28. Jan 17, 2018
  29. Jan 15, 2018
    • bruno mongazon's avatar
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX,... · cf0e9175
      bruno mongazon authored
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX, _RTAI_MATH_H, CELLULAR, TIMER_ONESHOT_MODE, EMOS, EMOS_CHANNEL, OAI_EMU, OPENAIR_EMU, PHY_ABSTRACTION, PHY_ABSTRACTION_UL removed
      cf0e9175
    • Cedric Roux's avatar
      Fix NFAPI integration · 922b5b59
      Cedric Roux authored
      This commit fixes issues introduced by the previous commit.
      
      Summary of work:
      - cleanup:
        - fix LOG_XX to be less verbose
        - fix cmake_targets/CMakeLists.txt
        - fix oaienv
        - remove dead code
      - bug fixes:
        - in openair1/SCHED/fapi_l1.c we had:
            eNB->pdcch_vars[subframe&1].num_dci           = number_dci;
          should be:
            eNB->pdcch_vars[subframe&1].num_dci           = 0;
          This bug let the PHY send more DCIs than what should have been
          sent because num_dci is incremented later on in the code.
          This fix may be a problem for fapi mode, to be checked.
        - add new T VCD traces
        - revert openair1/PHY/TOOLS/file_output.c to 'develop' version
        - remove thread_id in logRecord/logRecord_mt
        - revert (and adapt) configuration files
        - be careful when doing frame++, we need to % 1024
        - revert target_rx_power in openair2/LAYER2/MAC/eNB_scheduler_ulsch.c
      - NFAPI:
        - the open-nFAPI code has been included in the repository. See nfapi/README.
          Maybe we should "git clone" the Cisco repository instead. We have to be
          careful of availability though.
      
      What has been tested:
      - monolithic eNB FDD 5/10MHz with one UE, iperf UDP/TCP uplink/downlink
      
      Anything else may fail to work, especially the FAPI mode, which has not
      been tested at all.
      922b5b59
    • Cedric Roux's avatar
      import NFAPI work from David Price from Cisco (non-working commit, do not use it) · 7757b9e7
      Cedric 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
      9106438239e0bc626ff1fa1d97d911caadd0fbb9.
      
      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
  30. Jan 14, 2018
  31. Jan 11, 2018
Loading