Skip to content
Snippets Groups Projects
  1. Sep 20, 2017
  2. Sep 19, 2017
  3. Sep 16, 2017
  4. Sep 15, 2017
  5. Sep 14, 2017
  6. Sep 03, 2017
  7. Aug 17, 2017
  8. Aug 15, 2017
  9. Aug 14, 2017
  10. Aug 13, 2017
  11. Aug 11, 2017
  12. Aug 10, 2017
  13. Aug 08, 2017
  14. Jul 25, 2017
  15. Jul 24, 2017
  16. Jul 19, 2017
  17. Jul 06, 2017
  18. Jun 04, 2017
  19. May 22, 2017
  20. May 18, 2017
    • echigoya's avatar
      Fujitsu No.6 Correct DAI incrementation · d79c186a
      echigoya authored
      d79c186a
    • Cedric Roux's avatar
      warning removal · c08bd6ba
      Cedric Roux authored
      force j to -1, there is a compilation warning with the T tracer
      (variable may be used uninitialized)
      c08bd6ba
    • Cedric Roux's avatar
      minor: warnings removal · dcfdd761
      Cedric Roux authored
      It seems that ciphering_algorithm is "unsigned int" in RRC Rel10
      and "unsigned long" in RRC Rel14 (as processed by asn1c)
      
      Let's force it to unsigned long in the log to avoid compilation-time
      warnings.
      dcfdd761
    • Cedric Roux's avatar
      warnings removal in LOG_X · 9d65f4dd
      Cedric Roux authored
      those popped up thanks to previous commit
      9d65f4dd
    • Cedric Roux's avatar
      redo commit cb67d586 · 94dd8843
      Cedric Roux authored
      Seems like this commit got lost at some point.
      
      Here was the message:
      -----------------------------------------------------------------------------
      Author: Cedric Roux <cedric.roux@eurecom.fr>
      Date:   Tue Jan 10 14:21:02 2017 +0100
      
          add format indicator to get LOG_X warnings
      
          The LOG_X macros emit a lot of warnings when compiling with the T
          because they call the function logRecord (or logRecord_mt)
          which has not been "marked" as calling printf, so gcc won't
          emit typical printf warnings.
      
          With the T, they directly translate to sprintf, so those warnings
          pop up, much more verbose due to several macro expansions.
      
          Let's make them pop up all the time so it's easier to fix them.
      -----------------------------------------------------------------------------
      94dd8843
    • Cedric Roux's avatar
      add CQI to periodic logging of UE · f6693af6
      Cedric Roux authored
      f6693af6
  21. May 15, 2017
  22. May 13, 2017
    • Cedric Roux's avatar
      rewrite phy_stats_exist · 9eaee53b
      Cedric Roux authored
      We have to test that all active CCs of a given UE exist in the PHY layer.
      Maybe not the end of the story...
      9eaee53b
  23. May 12, 2017
    • Tien-Thinh Nguyen's avatar
      fix the errors related to multiple carriers (for a given UE considering only... · 3d4ba1a3
      Tien-Thinh Nguyen authored
      fix the errors related to multiple carriers (for a given UE considering only the CCs which this UE belongs to)
      3d4ba1a3
    • gabrielC's avatar
      bug fixes from Fujitsu (bug 26) · 899d1506
      gabrielC authored
      ----------------------------------------------------------
      bug 26
      
      Ttile:
      g_buffer has only 32 index, but he/she tries to zero clear
      1024 index.
      
      Bug Location:
      static uint8_t g_buffer[32];
      :
      memset (g_buffer, 0, 1024);
      
      Note:
      Detected by CppCheck
      ----------------------------------------------------------
      899d1506
    • gabrielC's avatar
      bug fixes from Fujitsu (bug 21) · 98a7a16e
      gabrielC authored
      Note: this fix does not solve the issue with how
      this buffer is used in this function, but I'm not
      sure this code is used at all (Cédric Roux).
      
      ----------------------------------------------------------
      bug 21
      
      Ttile:
      PAYLOAD_MAX=1500, so this coding results in index overflow.
      Additionally, operator "!=" just compairs something, this
      coding is meaningless.
      
      Bug Location:
      buffer[PAYLOAD_MAX] != '\0';
      
      Note:
      Detected by CppCheck
      ----------------------------------------------------------
      98a7a16e
  24. May 03, 2017
  25. Apr 25, 2017
  26. Apr 18, 2017
Loading