From 9fa0cce100d25585f5a1baff3353cd54a5a58d5f Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Fri, 1 Jul 2011 18:09:34 +0200 Subject: fix BTS initialization order The sequence is as follows: 0) start osmo-bts 1) start connection attempts to BTS 2) issue L1-RESET.req 3) receive L1-RESET.conf 4) issue RF-ACTIVATE.req 5) receive RF-ACTIVATE.conf 6) receive attributes for TRX 7) receive opstart for TRX 8) issue MPH-INIT.req [...] The important point here is: We don't want the BSC to set TRX attributes or do TRX opstart before our RF related hardware is initialized. --- include/osmo-bts/bts.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'include') diff --git a/include/osmo-bts/bts.h b/include/osmo-bts/bts.h index 1a5a7fd6..92be011c 100644 --- a/include/osmo-bts/bts.h +++ b/include/osmo-bts/bts.h @@ -6,7 +6,7 @@ extern void *tall_bts_ctx; int bts_init(struct gsm_bts *bts); -void bts_shutdown(struct gsm_bts *bts); +void bts_shutdown(struct gsm_bts *bts, const char *reason); struct gsm_bts *create_bts(uint8_t num_trx, char *id); int create_ms(struct gsm_bts_trx *trx, int maskc, uint8_t *maskv_tx, -- cgit v1.2.3