This only works for a UE with primary CC = 0 and secondary CC = 1.
Many values are also hardcoded.

When receiving an uplink ACK/NACK we send SINR of 20dB
to the libscheduler. If we don't send this information
the scheduler does not activate 16QAM for uplink transmission.

We could do it at any time, this is has been chosen arbitrarily.

The libscheduler does not return a correct rbBitmap
(as far as I understand).

Let's memorize the one used for 1st transmission and reuse it.

If there are two or more UEs in the system then things may
fail if the scheduler allocates the PRBs used by UE 1 in 1st
transmission to UE 2 at the same time of a retransmission for
UE 1.

to be removed at some point

The UE sends 2 bits when a second CC is configured, even when
the 2nd carrier is not activated. At least, this is what I
understand and this seems to be what happens with the sequans UE.

this commit is a first step to have the softmodem work with 2 CCs
with the FAPI scheduler.

there is still work to do for it to work properly.

the trace ENB_MASTER_TICK did not work properly in the GUI of
the enb tracer.

Maybe use proc->subframe_tx (or _rx) instead of this proposed
solution, maybe more elegant?

was crashing the processing

important for carrier aggregation case

especially when 2 CCs configured (ie. the UE can do carrier aggregation)

Merge remote-tracking branch 'origin/feature-15-carrier_aggregation' into feature-31-ff-scheduler-api

 Conflicts:
    cmake_targets/CMakeLists.txt
    openair1/PHY/LTE_TRANSPORT/dci_tools.c
    openair1/PHY/LTE_TRANSPORT/pucch.c
    openair1/SCHED/phy_procedures_lte_eNb.c
    openair2/LAYER2/MAC/eNB_scheduler_dlsch.c
    openair2/LAYER2/MAC/proto.h
    openair2/RRC/LITE/rrc_eNB.c

define MEGALOG at compile time to get them

Conflicts:
	cmake_targets/build_oai
	openair2/RRC/LITE/rrc_eNB.c

Resolve "OAI-UE, DFT segmentation fault"

Closes #130

See merge request !42

Merge branch '130-oai-ue-dft-segmentation-fault' of https://gitlab.eurecom.fr/oai/openairinterface5g into 130-oai-ue-dft-segmentation-fault

If your configuration file does not contain a parameter
the softmodem only printed "Failed to parse eNB configuration file"
without telling you what parameter was not found.

This quick fix adds a warning in such cases.

It also exists at the first error rather than trying to
parse the rest of the configuration file.

we have to lock when we dump to file in case of concurrent accesses

it's rare, but it happens

let's print an error in case of failure when trying to open it

it was 8 in the past
now it is 4
we should get the value from config, not hardcoded