This was causing oaisim to fail way too often at the startup
of a connection.

Things should go better with this patch.

It may not be the end of the story, the use of retrans_num_bytes_to_retransmit
is not clear to me. The problem I see is: what if the max number of
retransimission has been reached (if that has a meaning at all in RLC AM)?
will this value be decreased or not?

The code was changing the rnti in the red-black tree without
removing/reinserting the context. This is wrong because the
rnti is a key of the red-black tree and you cannot change the
key in a stored item at will.

There are also modifications of the function mac_eNB_rrc_ul_failure
which has to remove the UE in any case.

And rrc_mac_remove_ue has been changed for the case where
the UE is not found.

The distinction common space/user space still requires some
careful examination.

if you compile *without* T it fails because the T macro is interpreted
as a function call

(the T macro is then undefined)

- adding T macros here and there
- modify the T_messages.txt
- modify enb.c to trace them in the RRC view

plus add rrc connection setup complete tracing

bugfixing for UL. Remaining problems: CCE allocations in subframe 5 lead to occasional illegal DCI allocations (affects UL DCI which is missed by UE). waveform compliance with CQI in ULSCH.

probably not be here.

added hotfix for DCCH bad size limitation (to be checked after merge with develop).  Changed UL idle scheduling to improve 5MHz performance, changed DCI aggregation for ue-specific DCIs (reduces contention with SI and RA in subframe 5 for 5 MHz). Added RRC timer for UE release which cleans L1.  Still issues in 10 MHz throughput with TCP. 5 MHz seems almost fine.

it was at the wrong place
it was also wrong (< instead of <=)