Skip to content
Snippets Groups Projects
  1. Sep 05, 2018
  2. Sep 03, 2018
  3. Aug 23, 2018
  4. Aug 20, 2018
  5. Jul 30, 2018
  6. Jun 25, 2018
  7. Jun 03, 2018
  8. Jun 02, 2018
  9. May 24, 2018
  10. May 22, 2018
  11. May 18, 2018
  12. May 16, 2018
  13. May 14, 2018
  14. May 09, 2018
  15. Apr 29, 2018
  16. Apr 25, 2018
  17. Apr 22, 2018
  18. Apr 17, 2018
  19. 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
      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
  20. Apr 12, 2018
  21. Apr 10, 2018
  22. Apr 09, 2018
  23. Apr 06, 2018
Loading