aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2021-01-25 11:31:57 +0100
committerPau Espin Pedrol <pespin@sysmocom.de>2021-01-25 11:31:59 +0100
commit8f1701fe24b684486476656d3d38f1ce793bb987 (patch)
tree490cf4c01379ef4e4fde12697bff7ec2927b273d
parent0298c0b6a018f66639821a3f186bbaa7644780ed (diff)
sched: Check if egprs is enabled in TBF rather than MS being egprs capable
It could happen as of current implementation that a TBF was created as GPRS due to the MS being non-egprs, and later on the MS was upgraded to EGPRS due to newly received information from the MS. Hence, in order to infer if the data block is EGPRS or GPRS, let's better check for the TBF info, which is the one really mandating the kind of dl block to generate. Change-Id: I49720fb3a69ca972cd1973de937ac8ee77615431
-rw-r--r--src/gprs_rlcmac_sched.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gprs_rlcmac_sched.cpp b/src/gprs_rlcmac_sched.cpp
index 56401580..49a8ff26 100644
--- a/src/gprs_rlcmac_sched.cpp
+++ b/src/gprs_rlcmac_sched.cpp
@@ -341,7 +341,7 @@ static struct msgb *sched_select_downlink(struct gprs_rlcmac_bts *bts,
pdch->next_dl_tfi = (prio_tfi + 1) & 31;
/* generate DL data block */
msg = prio_tbf->create_dl_acked_block(fn, ts, req_mcs_kind);
- *is_egprs = ms_mode(prio_tbf->ms()) != GPRS;
+ *is_egprs = prio_tbf->is_egprs_enabled();
}
return msg;