From 9fa0cce100d25585f5a1baff3353cd54a5a58d5f Mon Sep 17 00:00:00 2001
From: Harald Welte <laforge@gnumonks.org>
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.
---
 src/osmo-bts-sysmo/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/osmo-bts-sysmo/main.c')

diff --git a/src/osmo-bts-sysmo/main.c b/src/osmo-bts-sysmo/main.c
index cf6aeae9..07ed8dcb 100644
--- a/src/osmo-bts-sysmo/main.c
+++ b/src/osmo-bts-sysmo/main.c
@@ -170,7 +170,7 @@ static void signal_handler(int signal)
 	switch (signal) {
 	case SIGINT:
 		//osmo_signal_dispatch(SS_GLOBAL, S_GLOBAL_SHUTDOWN, NULL);
-		bts_shutdown(bts);
+		bts_shutdown(bts, "SIGINT");
 		break;
 	case SIGABRT:
 	case SIGUSR1:
-- 
cgit v1.2.3