Skip to content
Snippets Groups Projects
  1. Jul 30, 2018
  2. May 11, 2018
    • Cedric Roux's avatar
      fix rdtsc usage · ad46183e
      Cedric Roux authored
      One user had a problem compiling oaisim.
      This commit fixes it.
      
      The compilation log was saying:
      
          targets/RT/USER/lte-ue.c:
          In function UE_thread_rxn_txnp4:
      
          openair2/UTIL/LOG/log.h:370:3:
          error: inconsistent operand constraints in an asm
      
               __asm__ volatile ("rdtsc" : "=a" (a), "=d" (d));
      
               ^
      ad46183e
  3. Apr 29, 2018
  4. Apr 24, 2018
  5. Apr 09, 2018
  6. Apr 08, 2018
  7. Mar 08, 2018
  8. Jan 16, 2018
  9. Jan 15, 2018
    • bruno mongazon's avatar
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX,... · cf0e9175
      bruno mongazon authored
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX, _RTAI_MATH_H, CELLULAR, TIMER_ONESHOT_MODE, EMOS, EMOS_CHANNEL, OAI_EMU, OPENAIR_EMU, PHY_ABSTRACTION, PHY_ABSTRACTION_UL removed
      cf0e9175
    • 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
      9106438239e0bc626ff1fa1d97d911caadd0fbb9.
      
      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
  10. Jan 11, 2018
  11. Dec 09, 2017
  12. Nov 22, 2017
  13. Nov 03, 2017
  14. Oct 23, 2017
  15. Oct 19, 2017
    • Cedric Roux's avatar
      remove gcc warnings · f1e8bff3
      Cedric Roux authored
      phy_init_lte_ue_signal was renamed init_lte_ue_signal in openair1/PHY/INIT/defs.h
      maybe it's the opposite that should have been done?
      
      Functions used in one file and defined in another may have been
      declared in the wrong header file.
      f1e8bff3
  16. Oct 01, 2017
  17. Sep 28, 2017
  18. Aug 07, 2017
    • Cedric Roux's avatar
      fix vcd · 309ca066
      Cedric Roux authored
      several problems were present:
      - there was no comma after "ue0_trx_write_ns_missing" in the array
        eurecomVariablesNames;
        comma was put, and also commas for the last element in the array,
        which doesn't hurt and will prevent future problems
      - bad order of values in eurecomVariablesNames, which
        was different from the enum vcd_signal_dump_variables;
        order was checked and fixed
      - strange/wrong use of VCD_SIGNAL_DUMPER_MODULE_END/LAST;
        the whole logic was removed/simplified
      309ca066
  19. Jul 06, 2017
  20. Jun 04, 2017
  21. Jun 02, 2017
    • Frank A. Zdarsky's avatar
    • Cedric Roux's avatar
      integration fixes · 60c4b5ec
      Cedric Roux authored
      - rename UE_NO_LOG to DISABLE_LOG_X
        because the name is misleading. The full software
        is impacted, not only the UE part
      - same for compilation option ---ue-no-log
        that becomes --disable-log
      - keep LOG_X for the standard case, that is the
        case without DISABLE_LOG_X where printf has been
        put. Two reasons:
        * printf is not realtime friendly
        * keep behavior similar for other users who may
          be troubled by different logs that don't add
          any benefit to previous logs
      60c4b5ec
  22. May 22, 2017
  23. May 19, 2017
  24. May 18, 2017
    • 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
  25. May 12, 2017
    • 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
  26. Apr 18, 2017
  27. Apr 17, 2017
  28. Apr 03, 2017
    • Cedric Roux's avatar
      integration fix: fixes for pthread_getname_np · c36c0453
      Cedric Roux authored
      - define _GNU_SOURCE before including pthread.h
      - do not use static for the array 'threadname' used
        to store the name, it makes it a global variable
        accessed by several threads in parallel
      - increase size of 'threadname' (maybe not necessary)
      - properly indent #define / #under (# should be at column 1)
      c36c0453
  29. Mar 28, 2017
  30. Mar 27, 2017
  31. Feb 23, 2017
    • Cedric Roux's avatar
      hotfix: pass "%s" to LOG_W to avoid compilation warnings · 60b83d84
      Cedric Roux authored
      The warning was:
      
      ------------------------
      In file included from /roux/openairinterface5g/openair2/UTIL/LOG/log.h:306:0,
                       from /roux/openairinterface5g/openair1/PHY/defs.h:54,
                       from /roux/openairinterface5g/openair2/LAYER2/MAC/eNB_scheduler_ulsch.c:33:
      /roux/openairinterface5g/openair2/UTIL/LOG/log.h: In function 'printMeas':
      /roux/openairinterface5g/common/utils/T/T.h:94:26: warning: format not a string literal and no format arguments [-Wformat-security]
       #define T_ID(x) ((struct T_header *)(uintptr_t)(x))
                                ^
      /roux/openairinterface5g/common/utils/T/T.h:29:22: note: in definition of macro 'T_PUT_int'
           int T_PUT_var = (val); \
                            ^
      /roux/openairinterface5g/common/utils/T/T.h:269:7: note: in expansion of macro 'T_HEADER'
             T_HEADER(t); \
             ^
      /roux/openairinterface5g/common/utils/T/T.h:101:76: note: in expansion of macro 'T3'
               n18,n19,n20,n21,n22,n23,n24,n25,n26,n27,n28,n29,n30,n31,n32,n,...) T##n
                                                                                  ^
      /roux/openairinterface5g/common/utils/T/T.h:102:16: note: in expansion of macro 'TN'
       #define T(...) TN(__VA_ARGS__)
                      ^
      /roux/openairinterface5g/openair2/UTIL/LOG/log.h:308:28: note: in expansion of macro 'T'
       #    define LOG_W(c, x...) T(T_LEGACY_ ## c ## _WARNING, T_PRINTF(x))
                                  ^
      /roux/openairinterface5g/common/utils/T/T_IDs.h:71:30: note: in expansion of macro 'T_ID'
       #define T_LEGACY_PHY_WARNING T_ID(68)
                                    ^
      /roux/openairinterface5g/openair2/UTIL/LOG/log.h:308:30: note: in expansion of macro 'T_LEGACY_PHY_WARNING'
       #    define LOG_W(c, x...) T(T_LEGACY_ ## c ## _WARNING, T_PRINTF(x))
                                    ^
      /roux/openairinterface5g/openair2/UTIL/LOG/log.h:411:9: note: in expansion of macro 'LOG_W'
               LOG_W(PHY,txt2);
      ------------------------
      
      over and over.
      
      By replacing LOG_W(PHY,txt2) by LOG_W(PHY,"%s",txt2) all the warnings
      are removed.
      60b83d84
  32. Feb 17, 2017
    • Cedric Roux's avatar
      warning fix: remove pragma in LFDS · 74afbf84
      Cedric Roux authored
      Not sure that it's correct, but those #pragma seem
      to be of no use for gcc. Let's remove them
      completely.
      74afbf84
    • Cedric Roux's avatar
      Revert "fix nettle" · 76574a1a
      Cedric Roux authored
      This reverts commit d31634c3.
      
      Laurent Thomas had a problem on one machine with the build_oai
      way of checking for nettle.
      
      The problem with the alternative solution of including nettle/bignum.h
      is that it is very unclear.
      
      The problem with nettle is that the file nettle/config.h does not
      exist for version 2. It was introduced in version 3.
      
      We want to support both versions, but there is an API incompatibility.
      So we need an #if #else mechanism.
      
      The file nettle/bignum.h is present in both versions 2 and 3 and it
      includes nettle/version.h in the version 3.
      
      So by including this file, we can check for the existence of
      NETTLE_VERSION_MAJOR (that comes from nettle/config.h) in the
      code.
      
      But as you can see, the reasoning is way too complex.
      
      So it's better to keep the check in cmake_targets/CMakeLists.txt.
      
      As long as we support version 2 this will be the way to go.
      
      It is possible to force a given version in specific non-generic
      customized environments.
      76574a1a
Loading