diff options
| author | Vadim Yanitskiy <vyanitskiy@sysmocom.de> | 2022-03-18 03:57:01 +0300 |
|---|---|---|
| committer | fixeria <vyanitskiy@sysmocom.de> | 2022-04-05 13:45:31 +0000 |
| commit | bd7ef4101b3fdfdac835f1f3c68832217b987444 (patch) | |
| tree | 8717a3b497cd34235e6ef5c5e335e6d11d21f8ca /include | |
| parent | 7a2f307246973ffa89a1fb667652f0b8ba7208c1 (diff) | |
osmo-bts-trx: rx_tchh_fn(): indicate BER10k=0 for FACCH BFIs
It makes no sense to store BER10k value of an Uplink FACCH frame
in order to indicate it in a BFI later on. Given that these BFIs
are generated artificially, it's fine to indicate BER10k=0.
Change-Id: I24d12892760dca0ad0a5c2abca9fc66523d9e614
Related: I1ad9fa3815feb2b4da608ab7df716a87ba1f2f91
Diffstat (limited to 'include')
| -rw-r--r-- | include/osmo-bts/scheduler.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/osmo-bts/scheduler.h b/include/osmo-bts/scheduler.h index 1e1a2d72..2806117b 100644 --- a/include/osmo-bts/scheduler.h +++ b/include/osmo-bts/scheduler.h @@ -126,7 +126,6 @@ struct l1sched_chan_state { uint8_t dl_ongoing_facch; /* FACCH/H on downlink */ uint8_t ul_ongoing_facch; /* FACCH/H on uplink */ struct l1sched_meas_set meas_avg_facch; /* measurement results for last FACCH */ - uint16_t ber10k_facch; /* bit error rate for last FACCH */ uint8_t dl_facch_bursts; /* number of remaining DL FACCH bursts */ |