This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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, master has been updated via 84e4dd92d454cd58e9cbe127c0d969e248f0e588 (commit) via 55da9874c0306516b8f3bb6f1db486a3c9c51fb2 (commit) via d8d5f5904fa83786b01dbf77593232eb6f6954bc (commit) via 9acc82ce4a01d502db1be8cdf15d2328ae181c5c (commit) via c017e309c4d73420a31c32e95aeae30f5e09c161 (commit) via 2e59b20204e2ebcf5baff60774f0fd4ac707404f (commit) via fd425b1484ceac900c02f7d8fcb5fb199ef2bbf6 (commit) via 50131c125e2298cc4f71fa2b69881f6a40a7000a (commit) via 5a03e129a633637d0a6b57b3b5aa6d6596b938fe (commit) from b7ebf545e6cc5eee17df254815c7838fbea61db7 (commit) 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=84e4dd92d454cd58e9cbe127c0d969e248f0e588 commit 84e4dd92d454cd58e9cbe127c0d969e248f0e588 Author: Holger Hans Peter Freyther <holger at moiji-mobile.com> Date: Fri Jan 9 22:06:28 2015 +0100 sysmobts: Improve some log messages for calib control * Print the GPS FD that was opened (e.g. to see if it was closed again) * Print the state changes/expectations * Print the correct to be applied. I wondered if I shouldo do a cor = cor * -1.. cor = -cor.. or add CLOCK_CORR(err) macro to use it inside the printf and correction and decided the gain is not worth the risk. http://cgit.osmocom.org/osmo-bts/commit/?id=55da9874c0306516b8f3bb6f1db486a3c9c51fb2 commit 55da9874c0306516b8f3bb6f1db486a3c9c51fb2 Author: Holger Hans Peter Freyther <holger at 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=d8d5f5904fa83786b01dbf77593232eb6f6954bc commit d8d5f5904fa83786b01dbf77593232eb6f6954bc Author: Holger Hans Peter Freyther <holger at 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=9acc82ce4a01d502db1be8cdf15d2328ae181c5c commit 9acc82ce4a01d502db1be8cdf15d2328ae181c5c Author: Holger Hans Peter Freyther <holger at 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. Work around trimble decoding issues (sent an email upstream). We need to gain some more experience to see if there memory leaks. We also need to re-schedule the calibration depending on the outcome. http://cgit.osmocom.org/osmo-bts/commit/?id=c017e309c4d73420a31c32e95aeae30f5e09c161 commit c017e309c4d73420a31c32e95aeae30f5e09c161 Author: Holger Hans Peter Freyther <holger at moiji-mobile.com> Date: Tue Jan 6 19:11:49 2015 +0100 sysmobts: The correction for GPS is in the reverse direction Change the sign before passing it as correction value. The error is the difference between the TCXO and GPS. We need to correct by the reverse of the error. This seems to be different depending on the clock source we have. This is a last minute untested change. http://cgit.osmocom.org/osmo-bts/commit/?id=2e59b20204e2ebcf5baff60774f0fd4ac707404f commit 2e59b20204e2ebcf5baff60774f0fd4ac707404f Author: Holger Hans Peter Freyther <holger at 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=fd425b1484ceac900c02f7d8fcb5fb199ef2bbf6 commit fd425b1484ceac900c02f7d8fcb5fb199ef2bbf6 Author: Holger Hans Peter Freyther <holger at 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=50131c125e2298cc4f71fa2b69881f6a40a7000a commit 50131c125e2298cc4f71fa2b69881f6a40a7000a Author: Holger Hans Peter Freyther <holger at 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=5a03e129a633637d0a6b57b3b5aa6d6596b938fe commit 5a03e129a633637d0a6b57b3b5aa6d6596b938fe Author: Holger Hans Peter Freyther <holger at 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/common/msg_utils.c | 18 +- src/osmo-bts-sysmo/Makefile.am | 5 +- src/osmo-bts-sysmo/misc/sysmobts_mgr.c | 9 + src/osmo-bts-sysmo/misc/sysmobts_mgr.h | 36 ++ src/osmo-bts-sysmo/misc/sysmobts_mgr_calib.c | 538 +++++++++++++++++++++++++++ src/osmo-bts-sysmo/misc/sysmobts_mgr_vty.c | 16 + src/osmo-bts-sysmo/sysmobts_ctrl.c | 17 + 8 files changed, 630 insertions(+), 10 deletions(-) create mode 100644 src/osmo-bts-sysmo/misc/sysmobts_mgr_calib.c hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)