From 72c735603e9dac88e0ae75ab080f450db9c5ad6a Mon Sep 17 00:00:00 2001 From: Philipp Maier Date: Tue, 12 Oct 2021 15:36:18 +0200 Subject: [PATCH] osmo_bsc_main: remove not longer needed fixme note It is not possible to operate a cell that has secondary TRXs in different bands. Especially considering that DCS1800 and PCS1900 have overlapping ARFCN numbers it would be hard for the MS to tell to which band it should switch. Also the ImmAss. message only contains the ARFCN number. It is impractical to have TRXs in different bands and probably this also violates the sepec. Change-Id: Icc2af9e2a9bca3897dbbb34d7b2c0fe6f843bedd --- src/osmo-bsc/osmo_bsc_main.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/osmo-bsc/osmo_bsc_main.c b/src/osmo-bsc/osmo_bsc_main.c index 3a1a6731e..92b74753f 100644 --- a/src/osmo-bsc/osmo_bsc_main.c +++ b/src/osmo-bsc/osmo_bsc_main.c @@ -446,8 +446,6 @@ static int bootstrap_bts(struct gsm_bts *bts) if (!bts->model) return -EFAULT; - /* FIXME: What about secondary TRX of a BTS? What about a BTS that has TRX - * in different bands? Why is 'band' a parameter of the BTS and not of the TRX? */ switch (bts->band) { case GSM_BAND_1800: if (bts->c0->arfcn < 512 || bts->c0->arfcn > 885) {