An error occurred fetching the project authors.
- 02 Jun, 2018 1 commit
-
-
Raymond Knopp authored
-
- 29 Apr, 2018 1 commit
-
-
Raymond Knopp authored
-
- 16 Apr, 2018 1 commit
-
-
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.
-
- 09 Apr, 2018 1 commit
-
-
Raymond Knopp authored
-
- 06 Apr, 2018 1 commit
-
-
Raymond Knopp authored
-
- 05 Apr, 2018 1 commit
-
-
Raymond Knopp authored
-
- 20 Mar, 2018 1 commit
-
-
Raymond Knopp authored
-
- 16 Mar, 2018 1 commit
-
-
Wang Tsu-Han authored
-
- 15 Mar, 2018 1 commit
-
-
Cedric Roux authored
The code is too complex. This commit may not be enough.
-
- 08 Mar, 2018 1 commit
-
-
oai authored
-
- 23 Feb, 2018 1 commit
-
-
Wang Tsu-Han authored
-
- 22 Feb, 2018 3 commits
-
-
Cedric Roux authored
-
Cedric Roux authored
- remove spaces at the end of lines - remove useless dead code use: git show -p <this commit> -w to see it clearly
-
Cedric Roux authored
With value 4 when connecting one UE and doing some downlink iperf TCP there is a crash. Probably due to the multiple wrong RA detected leading to uplink failure of fake UE that never sends Msg3 (because, well, there is no other UE). This is another problem that will be fixed at some point. Anyway, this value 4 fails. Let's put back 3.
-
- 20 Feb, 2018 1 commit
-
-
Wang Tsu-Han authored
-
- 19 Feb, 2018 1 commit
-
-
Wolfgang A. Mozart authored
-
- 17 Feb, 2018 1 commit
-
-
Raymond Knopp authored
-
- 16 Feb, 2018 1 commit
-
-
Wang Tsu-Han authored
-
- 14 Feb, 2018 1 commit
-
-
Cedric Roux authored
Doing airplane mode off to connect a cots UE followed by airplane mode on to disconnect it gives very bad results (bad disconnection with lots of UL failures followed by lots of logs in the eNB). It used to work properly after the work done by Xu Bo. It turns out that in 2018.w04 things were still working okay. But in 2018.w05 no. So I ran: git diff 2018.w04 2018.w05 And I checked all the modifications that I thought were relevant (everything related to the UE, oaisim, if4 and fapi has not been checked). This commits takes back the version of 2018.w04. The modifications in openair2/RRC/LITE/rrc_eNB.c are necessary, I think. The other modifications may not be necessary or even wrong. To be checked at some point.
-
- 13 Feb, 2018 1 commit
-
-
Raymond Knopp authored
-
- 22 Jan, 2018 1 commit
-
-
Massive authored
adding an addition error check on harq_pid as it is sometimes not in range. root cause still to be identified
-
- 21 Jan, 2018 1 commit
-
-
Rohit Gupta authored
fixes after merge with develop. Partial UE/eNB separation in build to avoid problems with NFAPI in oaisim UE/RRU. tested with simulator.
-
- 17 Jan, 2018 1 commit
-
-
Eurecom authored
-
- 15 Jan, 2018 3 commits
-
-
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
-
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.
-
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.
-
- 10 Jan, 2018 1 commit
-
-
Younes authored
-
- 08 Jan, 2018 1 commit
-
-
Xu Bo authored
-
- 03 Jan, 2018 1 commit
-
-
Wang Tsu-Han authored
-
- 14 Dec, 2017 1 commit
-
-
Wang Tsu-Han authored
-
- 24 Nov, 2017 1 commit
-
-
Wang Tsu-Han authored
-
- 17 Nov, 2017 1 commit
-
-
Wang Tsu-Han authored
-
- 10 Nov, 2017 1 commit
-
-
Wang Tsu-Han authored
-
- 02 Nov, 2017 1 commit
-
-
Wang Tsu-Han authored
-
- 25 Oct, 2017 1 commit
-
-
Cedric Roux authored
- remove global variables in the function lte_est_timing_advance_pusch - do the smoothing logic that was in lte_est_timing_advance_pusch in rx_sdu (is it necessary? is it correct?) - put back the value 100 in prach_procedures for the test on prach energy - change the value of timing_advance_update it was: timing_advance_update = sync_pos - eNB->frame_parms.nb_prefix_samples/4; //to check it is now: timing_advance_update = sync_pos; // - eNB->frame_parms.nb_prefix_samples/4; //to check this should be checked somehow. The computation looked suspicious. Maybe the new one is wrong.
-
- 23 Oct, 2017 3 commits
-
-
Wang Tsu-Han authored
added numerology paramter
-
Cedric Roux authored
-
Cedric Roux authored
just a quick fix before merge, the real solution is to disable pusch scheduling in the prach, to be done later
-
- 22 Oct, 2017 1 commit
-
-
Raymond Knopp authored
-
- 19 Oct, 2017 1 commit
-
-
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.
-