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, daniel/oml-state-fixes has been created at 78d0dffb8ff2d11c155ffbe2c9069db50cc34f74 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=78d0dffb8ff2d11c155ffbe2c9069db… commit 78d0dffb8ff2d11c155ffbe2c9069db50cc34f74 Author: Daniel Willmann <daniel(a)totalueberwachung.de> Date: Thu May 14 11:30:07 2015 +0200 common/oml: Ignore previous operational state for radio carrier opstart http://cgit.osmocom.org/osmo-bts/commit/?id=bf1ee561cd00addb152f723dee884e8… commit bf1ee561cd00addb152f723dee884e89be26a27e Author: Daniel Willmann <daniel(a)totalueberwachung.de> Date: Thu May 14 10:36:11 2015 +0200 osmo-bts: Change log message from debug to warning This is an abnormal condition that should not happen regularily. http://cgit.osmocom.org/osmo-bts/commit/?id=c1f78e4de8d741c849b68b1e7b1b504… commit c1f78e4de8d741c849b68b1e7b1b5042bbef34a5 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sun May 10 16:05:08 2015 +0200 osmo-bts-sysmo/oml.c: Update opstate and avstate after rf_lock completes According to 3GPP TS 12.21 Ch. 5.3: The admin state can be used to control the power of a trx by setting it to locked or unlocked. As a result when the operation completes the trx should set its operational state to disabled and the availability to off-line (if locked) or enabled and ok (if unlocked). Before this patch that didn't happen and so the nitb would still list all trx as operational/ok even after the trx has been switched off. The spec doesn't clearly recommend setting opstate to disabled, but that is what the nanoBTS does, so mimic its behaviour. ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)