1. 30 Jul, 2018 2 commits
  2. 25 Jun, 2018 1 commit
  3. 03 Jun, 2018 1 commit
  4. 02 Jun, 2018 1 commit
  5. 24 May, 2018 3 commits
  6. 22 May, 2018 1 commit
  7. 18 May, 2018 1 commit
  8. 17 May, 2018 1 commit
  9. 14 May, 2018 1 commit
  10. 10 May, 2018 1 commit
  11. 09 May, 2018 3 commits
  12. 29 Apr, 2018 1 commit
  13. 26 Apr, 2018 1 commit
  14. 25 Apr, 2018 1 commit
  15. 23 Apr, 2018 1 commit
  16. 22 Apr, 2018 1 commit
  17. 17 Apr, 2018 1 commit
  18. 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
      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
  19. 12 Apr, 2018 1 commit
  20. 10 Apr, 2018 1 commit
  21. 09 Apr, 2018 2 commits
  22. 06 Apr, 2018 1 commit
  23. 04 Apr, 2018 1 commit
  24. 26 Mar, 2018 1 commit
    • HARADA Masayuki's avatar
      Fix ul scd problems. · 5646b078
      HARADA Masayuki authored
      ・Delete double BSR calculation.
      ・change TBS for mcs setting bit to byte.
      
      (cherry picked from commit 39cd022424ebe98c95be32cbb4127aa9d0e0ff3b)
      5646b078
  25. 19 Mar, 2018 1 commit
    • Cedric Roux's avatar
      bugfix: send UL NACK (on PHICH) at the right place · d3938147
      Cedric Roux authored
      The PHICH was not programmed for the last round (4) because it was
      not programmed in rx_sdu but in schedule_ulsch_rnti, only in case
      of a programmed retransmission (there is obviously no retransmission
      programmed after the last round).
      
      The case of Msg3 is not handled. To be done somehow.
      d3938147
  26. 12 Mar, 2018 2 commits
  27. 08 Mar, 2018 1 commit
  28. 06 Mar, 2018 1 commit
  29. 01 Mar, 2018 1 commit
  30. 28 Feb, 2018 1 commit
  31. 22 Feb, 2018 1 commit
  32. 20 Feb, 2018 1 commit
  33. 15 Feb, 2018 1 commit
    • Cedric Roux's avatar
      integration fix: set default max MCS for UL back to 20 · c0be5a12
      Cedric Roux authored
      Doing an iperf UDP uplink test, we could reach only 6Mb/s
      with very good radio conditions instead of around 8Mb/s.
      
      It turns out the MCS was limited to 16.
      
      With this commit, we are back to a bit more than 8Mb/s
      as it used to be.
      
      (This is with a 5MHz bandwidth.)
      c0be5a12