From: gitosis@osmocom.org Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Sun, 24 Aug 2014 15:30:09 GMT Message-ID: <201408241530.s7OFU9mR016999@git.osmocom.org> Subject: osmo-bts.git branch laforge/oml-router updated. 0.3.0-231-g54cbbb1 Message: 11 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, laforge/oml-router has been updated discards c8b1ca8c78f6f61339eb14e69bfe3594a826f08a (commit) discards ee07f21f050dae09f0d5c25dec5555e6374e4f94 (commit) discards ca18eefd2ee0bae57e08b5e0d462393d172abb80 (commit) discards c2d945d16ea8885a97d70b0432f03513cb72a3b1 (commit) discards b0f92fbca74479c35fbde0a91f280ff4f871144b (commit) discards 2175db3cdd54679d0477042be805f8e54e2c380d (commit) discards c14ef12f71b852e71e6573022a35d73d185b3701 (commit) via 54cbbb14503f3a99c13a882e67433b66c06235b9 (commit) via 3d836bcf3097d1fb09fd98eca10558b4fdb636c4 (commit) via 85c7e90f434192e4fd6713d219bc33e0a47f6cde (commit) via af066bab9dac8f52efad4d924b6dcc3bc3c64626 (commit) via c0a3030277ed1541bcbfd5f602ee6dbe906fac14 (commit) via be1898495977f1aa0db1f63c4158be7ec0d8218e (commit) via 9d0fd073e91d25bf61c19089a0c4e0ee35457446 (commit) via 8e4cc1cbb8946b53c929caa2bd4bbf2fd30588a5 (commit) via 993575bcd8ecb03a06cf5c5e507f4eceba91d40c (commit) via 0ff0f2d00f37cd82a21e4638d15a8bb736419c8a (commit) via d9a2aa8d9909d93d96e421c7cb727932445fa8ab (commit) via e43feaf231e08f108aafa26a7829820fad3447cb (commit) via fcca2e82184f8ece6a31db48abd77d560065b31f (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (c8b1ca8c78f6f61339eb14e69bfe3594a826f08a) \ N -- N -- N (54cbbb14503f3a99c13a882e67433b66c06235b9) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=54cbbb14503f3a99c13a882e67433b66c06235b9 commit 54cbbb14503f3a99c13a882e67433b66c06235b9 Author: Harald Welte Date: Mon Aug 18 19:14:58 2014 +0200 Have osmo-bts request OML routes for all its MOs at startup During OML link start-up, osmo-bts now requests a OML route for each of the managed objects that it currently implements. This is done via the 'ORC' (OML Router Control) protocol, which is encapsulated in the extended IPA_PROTO_OSMO multiplex. The responses (ACK/NACK) are not yet processed inside osmo-bts. http://cgit.osmocom.org/osmo-bts/commit/?id=3d836bcf3097d1fb09fd98eca10558b4fdb636c4 commit 3d836bcf3097d1fb09fd98eca10558b4fdb636c4 Author: Harald Welte Date: Mon Aug 18 19:12:47 2014 +0200 remove traces of the old 'oml router' Prior to the stand-alone OML router there were some early steps, specific to the sysmobts code, to inject OML messages from external programs. Remove that, as it is now obsolete. http://cgit.osmocom.org/osmo-bts/commit/?id=85c7e90f434192e4fd6713d219bc33e0a47f6cde commit 85c7e90f434192e4fd6713d219bc33e0a47f6cde Author: Harald Welte Date: Sun Aug 17 22:01:45 2014 +0200 A dedicated OML router program (osmobts-omlrouter) The idea of this OML router is to be the entity that connects the OML link to the BSC. osmo-bts as well as other programs like sysmobts-mgr and possibly more will then connect to the OML-router rather than the BSC. The point is that those "OML clients" can then register for certain OML messages (particularly the managed objects like TRX, etc.) which then get routed to them. This is particularly useful in the context of 'stacked' multi-TRX BTSs, where we will have two osmo-bts processes, one on each of the TRX, both connecting OML to the oml-router. Through their respective subscription of the baseband transceiver OML object, they will get routed the IPA CONNECT RSL message from the BSC, and both osmo-bts processes will establish independent RSL connections to the BSC. http://cgit.osmocom.org/osmo-bts/commit/?id=af066bab9dac8f52efad4d924b6dcc3bc3c64626 commit af066bab9dac8f52efad4d924b6dcc3bc3c64626 Author: Harald Welte Date: Mon Aug 18 22:46:42 2014 +0200 Use new libosmo-abis features to allow OML on non-standard TCP port If we run osmo-bts, osmobts-omlrouter and osmo-nitb or osmo-bsc on one machine, we cannot have both omlrouter and osmo-{nitb,bsc} listen on TCP Port 3002. This introduces a new 'oml remote-port <0-65535>' directive to the osmo-bts configuration to connect to sunch a non-standard port. ----------------------------------------------------------------------- Summary of changes: doc/control_interface.txt | 57 ++++++++++++++++++ include/osmo-bts/control_if.h | 3 + src/common/Makefile.am | 3 +- src/common/bts_ctrl_commands.c | 78 +++++++++++++++++++++++++ src/common/bts_ctrl_lookup.c | 104 +++++++++++++++++++++++++++++++++ src/common/tx_power.c | 12 ++-- src/common/vty.c | 15 ----- src/osmo-bts-sysmo/Makefile.am | 2 +- src/osmo-bts-sysmo/l1_if.c | 3 - src/osmo-bts-sysmo/main.c | 8 ++- src/osmo-bts-sysmo/misc/sysmobts_mgr.c | 3 +- src/osmo-bts-sysmo/sysmobts_ctrl.c | 22 ++++--- 12 files changed, 269 insertions(+), 41 deletions(-) create mode 100644 doc/control_interface.txt create mode 100644 include/osmo-bts/control_if.h create mode 100644 src/common/bts_ctrl_commands.c create mode 100644 src/common/bts_ctrl_lookup.c hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)