1. 20 Feb, 2019 1 commit
  2. 28 Sep, 2018 2 commits
  3. 31 Aug, 2018 1 commit
  4. 16 Aug, 2018 1 commit
    • Eino Virtanen's avatar
      USRP addressess and clock sources can be configured in the configuration file... · be0e4095
      Eino Virtanen authored
      USRP addressess and clock sources can be configured in the configuration file with the RU section with comma separated IP addresses in 'sdr_addrs' and with strings "internal"/"external"/"gpsdo" in 'clock_src'.
      
      TODO: Currently the driver picks the two first RX and TX channels when nb_tx and nb_rx are both set to 2. If a developers wants to force usage of two devices, 'set_rx_subdev_spec' and 'set_tx_subdev_spec' can be used to indicate to the driver so that antennas from separate devices will be used. To rephrase: until 4 antennas are supported by OAI, testing with two devices, so that antennas from both devices are used, requires manual configuration of which subdevices' antennas are used.
      
      Conflicts:
      	targets/ARCH/USRP/USERSPACE/LIB/usrp_lib.cpp
      be0e4095
  5. 30 Jul, 2018 2 commits
  6. 23 Jul, 2018 1 commit
  7. 04 Jun, 2018 1 commit
  8. 18 May, 2018 1 commit
  9. 19 Jan, 2018 1 commit
  10. 15 Jan, 2018 2 commits
    • 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
      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
  11. 11 Jan, 2018 2 commits
  12. 27 Dec, 2017 1 commit
  13. 14 Nov, 2017 1 commit
  14. 23 Oct, 2017 2 commits
  15. 27 Sep, 2017 1 commit
  16. 21 Sep, 2017 1 commit
  17. 22 Aug, 2017 1 commit
  18. 18 Aug, 2017 3 commits
  19. 14 Aug, 2017 1 commit
  20. 18 May, 2017 1 commit
  21. 14 Feb, 2017 1 commit
  22. 10 Feb, 2017 2 commits
  23. 09 Feb, 2017 2 commits
  24. 01 Feb, 2017 1 commit
  25. 29 Jan, 2017 1 commit
  26. 28 Jan, 2017 1 commit
  27. 15 Jan, 2017 1 commit
  28. 13 Jan, 2017 1 commit
  29. 03 Jan, 2017 1 commit
  30. 26 Dec, 2016 1 commit
  31. 23 Nov, 2016 1 commit