bts: use feature list instead of speech codec table

osmo-bts has a table of pchan/channel mode combinations for every
bts. This table models the codec capabilitys of the BTS hardware.
However, having the speech codec apabilities modeled inside the
BTS feature list would be much more comfortable and since the
feature list is communicated back to the BSC we would get the
codec capabilities inside the BSC domain as well.

- remove the pchan/channel mode tables
- set speech codec variants for each BTS type
- fix bts_supports_cm so that it queries the feature list

Change-Id: I977dc729ba856631245aedf76afd48eac92166f7

1 files changed, 0 insertions, 9 deletions

diff --git a/src/osmo-bts-octphy/l1_if.c b/src/osmo-bts-octphy/l1_if.c
index e5fcd98a..8dc3e8f1 100644
--- a/src/osmo-bts-octphy/l1_if.c
+++ b/src/osmo-bts-octphy/l1_if.c
@@ -76,14 +76,6 @@
 /* timeout until which we expect PHY to respond */
 #define CMD_TIMEOUT		5
 
-/* Table with channel rate / and codec configuration that are supported
- * by the hardware bts_supports_cm() */
-static const struct bts_cm bts_model_supported_cm[] = {
-	{ GSM_PCHAN_TCH_F, GSM48_CMODE_SPEECH_V1},
-	{ GSM_PCHAN_TCH_H, GSM48_CMODE_SPEECH_V1},
-	{ _GSM_PCHAN_MAX, 0 }
-};
-
 /* allocate a msgb for a Layer1 primitive */
 struct msgb *l1p_msgb_alloc(void)
 {
@@ -784,7 +776,6 @@ int bts_model_init(struct gsm_bts *bts)
 	bts->variant = BTS_OSMO_OCTPHY;
 	btsb = bts_role_bts(bts);
 	btsb->support.ciphers = CIPHER_A5(1) | CIPHER_A5(2) | CIPHER_A5(3);
-	btsb->support.cm = bts_model_supported_cm;
 
 	/* FIXME: what is the nominal transmit power of the PHY/board? */
 	bts->c0->nominal_power = 15;