tree 9833ff4c1d87c96db2df8a81fe4b9aa4ce584ed4
parent ae2c18c57b5b8d2133a42297fb7ce02a8f332cce
author Harald Welte <laforge@gnumonks.org> 1448012611 +0100
committer Harald Welte <laforge@gnumonks.org> 1448012611 +0100

Fix TSC/BSIC handling bug and remove bts->tsc

This fixes a bug in the following circumstances:
* BSIC is set to 0 in the config file
* No TSC is explicitly specified at the BST level in the config file

In this case, we ended up using BSIC=0 and TSC=7, as TSC=7 is our
default initialization value.

The TSC of the CCCH/BCCH must always be the BCC, which is the lower 3
bits of the BSIC.  Having configuration options for both the BSIC _and_
the TSC at the BTS level therefore makes no sense, as it only adds ways
in which users can configure non-oprational configurations.  So we
remove the bts->tsc member, and keep only the ts->tsc members that allow
us to configure a timeslot-specific TSC that's different from the BTS
TSC (= BCC).