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, zecke/sysmobts-calibration has been updated discards 8480fbf803b410b3c7b67ce5f970a7a38f151a2e (commit) discards 6d54dee99d578834fa177d9f2a049c752105f9c4 (commit) discards 2419e9ab3bf4fe58a2652c8d0133f7ad0eb7e74a (commit) discards f1cf0c29fd5467dc2cc49d2bc1c7b2d42478c14f (commit) discards 97b0f8dc07ede7181eead1eba414771e6af8452c (commit) discards 6c905943f93673ea5b5b21ac4ffcb549ac665d1c (commit) via 2eb9812ec53fcaccf5623a1b7aad7fd6373552e5 (commit) via cbe5e35c60c74cd511a6b4965aae7614863a393c (commit) via e4894b25e63b25ac3360a483113adc3e6818ae27 (commit) via 3d75cb056d4b67b6cd3aeb6c786a201c4f9a6638 (commit) via 2048b09a6443fab269ee2da55c32c4813482cad4 (commit) via 814ec0773161fb9d4074cf35edef2ab2c8b2ac65 (commit) via 1716cb479cfe1ddaa240e7ed1dc6a47f00bdc234 (commit) via c265bef48c414ca6c135f803c0c5dfdecbeece72 (commit) via 02a2afa962799c1519eb78cffa8877fd3da75b2e (commit) via ffc193443c177c3e41851c445c71fc1095ae2201 (commit) via 8968b48643686683046a0af403178960f8baf9ed (commit) via 641a9349317e7b9dec2e38b6cec02a1904267954 (commit) via 69897d7eed6dc2f992db3499bf9bfe0950f0b34a (commit) via 0d09e75f9ca09ddbfe10117f2f4caa8993eb9144 (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 (8480fbf803b410b3c7b67ce5f970a7a38f151a2e) \ N -- N -- N (2eb9812ec53fcaccf5623a1b7aad7fd6373552e5) 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=2eb9812ec53fcaccf5623a1b7aad7fd… commit 2eb9812ec53fcaccf5623a1b7aad7fd6373552e5 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Tue Dec 23 11:47:28 2014 +0100 sysmobts: Create a calibration loop that will be run Continously run the calibration process. Everytime we call the reset function classify the outcome. In case of a failure schedule the next command soon and otherwise wait several hours. Remember if the process was started through the VTY or the run loop. In case it can't be started immediately reset and schedule a new run. http://cgit.osmocom.org/osmo-bts/commit/?id=cbe5e35c60c74cd511a6b4965aae761… commit cbe5e35c60c74cd511a6b4965aae7614863a393c Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Tue Dec 23 09:45:55 2014 +0100 sysmobts: Start the calibration the first time the link is up After a reboot the system might have been off for a long time and the currently used value might be wrong. Remember that we never ran the calibration and execute it on start. http://cgit.osmocom.org/osmo-bts/commit/?id=e4894b25e63b25ac3360a483113adc3… commit e4894b25e63b25ac3360a483113adc3e6818ae27 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Mon Dec 22 18:24:57 2014 +0100 sysmobts: Initial version to use libgps to determine FIX state We should only calibrate the clock if there is a GPS fix. Start gpsd to determine if there is a fix or not. This commit lacks: * A timeout for getting the fix * Verifying that gps_open/gps_close can be done without leaking * Schedule synchronization after start and after failures, then after a long time of operation. http://cgit.osmocom.org/osmo-bts/commit/?id=3d75cb056d4b67b6cd3aeb6c786a201… commit 3d75cb056d4b67b6cd3aeb6c786a201c4f9a6638 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 21:54:43 2014 +0100 sysmobts: Use the ctrl interface for calibration This runs the entire procedure for calibration with reasonable error and success checking. It can be triggered from the VTY of the sysmobts-mgr right now. What is missing is to hook up with GPSD to check if the system has a fix and provide a mode that will continously run the calibration command. http://cgit.osmocom.org/osmo-bts/commit/?id=2048b09a6443fab269ee2da55c32c48… commit 2048b09a6443fab269ee2da55c32c4813482cad4 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 19:20:17 2014 +0100 sysmobts: Copy more of l1if_rf_clock_info_reset into the CTRL code The CTRL code should have used/extended the l1_if calibration code. The sysmobts-mgr code first needs to determine if the clock adjustment is necessary at all. This is done by first resetting the counters, then waiting, then asking for the diff and then applying the correction value. But the reference clock is only set by the application comand. Copy more code of l1if_rf_clock_info_reset to set the reference clock as value. This is leaving some todos inside the code that will be resolved as part of SYS#835. Related: SYS#835 http://cgit.osmocom.org/osmo-bts/commit/?id=814ec0773161fb9d4074cf35edef2ab… commit 814ec0773161fb9d4074cf35edef2ab2c8b2ac65 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 16:59:41 2014 +0100 sysmobts: Begin with calib control from the sysmobts manager In the long run we will connect to GPSD and wait for a fix and then run the calibration. The first step is to open (and re-open) the control connection to the BTS. As the connection is on localhost there should not be a computation overhead to always have the connection open. When connecting assume that the ASYNC connect worked directly as otherwise we get no notification of the failure. This looks like a "bug" of libosmo-abis that should check if the socket has been connected or not. http://cgit.osmocom.org/osmo-bts/commit/?id=1716cb479cfe1ddaa240e7ed1dc6a47… commit 1716cb479cfe1ddaa240e7ed1dc6a47f00bdc234 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 16:54:08 2014 +0100 msg: Generalize the message structure test This was taken out of LaF0rge's OML router branch and is now used by the extended calibration feature. ----------------------------------------------------------------------- Summary of changes: configure.ac | 1 + src/osmo-bts-sysmo/Makefile.am | 9 +- src/osmo-bts-sysmo/eeprom.c | 2 +- src/osmo-bts-sysmo/misc/sysmobts_eeprom.h | 2 +- src/osmo-bts-sysmo/misc/sysmobts_mgr.h | 29 +++- src/osmo-bts-sysmo/misc/sysmobts_mgr_2050.c | 20 +++ src/osmo-bts-sysmo/misc/sysmobts_mgr_calib.c | 189 ++++++++++++++++++++++++--- src/osmo-bts-sysmo/misc/sysmobts_mgr_temp.c | 70 ++++++++-- src/osmo-bts-sysmo/misc/sysmobts_mgr_vty.c | 122 ++++++++++++++++- src/osmo-bts-sysmo/misc/sysmobts_misc.h | 1 + src/osmo-bts-sysmo/misc/sysmobts_par.c | 36 ++++- src/osmo-bts-sysmo/misc/sysmobts_par.h | 2 + src/osmo-bts-sysmo/misc/sysmobts_util.c | 33 +++-- 13 files changed, 465 insertions(+), 51 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)