1. 23 Feb, 2021 2 commits
    • rmagueta's avatar
      Merge branch 'develop' into develop-SA-RA · de017ddb
      rmagueta authored
      # Conflicts:
      #	cmake_targets/CMakeLists.txt
      #	openair1/SIMULATION/NR_PHY/dlsim.c
      #	openair1/SIMULATION/NR_PHY/ulsim.c
      de017ddb
    • Remi Hardy's avatar
      Merge branch 'integration_2021_wk06_MR978' into 'develop' · d350895a
      Remi Hardy authored
      MR978 : 
      We have incorporated 5G NR nFAPI into the develop branch
      P5 and P7 interfaces for NR have been implemented. 
      With this MR, downlink transmission through nFAPI will be possible. 
      We have also made sure that 4G nFAPI can be used from within the develop branch.
      d350895a
  2. 22 Feb, 2021 3 commits
  3. 21 Feb, 2021 1 commit
  4. 18 Feb, 2021 1 commit
  5. 15 Feb, 2021 1 commit
  6. 12 Feb, 2021 5 commits
  7. 11 Feb, 2021 7 commits
  8. 10 Feb, 2021 2 commits
  9. 09 Feb, 2021 5 commits
  10. 08 Feb, 2021 8 commits
  11. 07 Feb, 2021 5 commits
    • Robert Schmidt's avatar
      Use the MAX_BWP_SIZE macro everywhere · e557c5ae
      Robert Schmidt authored
      e557c5ae
    • Robert Schmidt's avatar
      Skip DL HARQ feedbacks if the timing does not match · 20ba3b3e
      Robert Schmidt authored
      As the precedent commit, this commit deals with the realtime problems
      that we currently have on the CI bench.
      
      For DL HARQ feedback, nFAPI does not give us the HARQ process ID.
      Instead, we have to figure this out "from timing", i.e., if we trigger
      PUCCH reception, we will get a message with HARQ if we instructed the
      PHY to do so. If we have real-time problems, it seems (I cannot verify:
      don't have real time problems) that we do not get the nFAPI message with
      HARQ feedback. Thus, we need to skip the HARQ processes that should have
      been processed in the past, which happens in this commit.
      20ba3b3e
    • Robert Schmidt's avatar
      Search correct UL HARQ, don't assert on late slot · 237ed35c
      Robert Schmidt authored
      At the time of this commit, the CI has realtime issues. This can mean
      that the HARQ result is delivered in a delayed fashion. Before this
      commit, we were asserting on whether the slot corresponds to the HARQ
      process's expected feedback slot, but a particular feedback might be
      delayed under realtime issues, and we actually don't care about the
      timing since we get the HARQ process ID.
      
      Instead, we loop through the HARQ processes for which we wait for a
      feedback in the beginning until we have the right process (which did not
      seem to cause a problem till now, but who knows.
      237ed35c
    • Robert Schmidt's avatar
      f2ae4a4b
    • Robert Schmidt's avatar
      Fix whitespace issues (review request) · d4151a9a
      Robert Schmidt authored
      d4151a9a