osmo-bts.git branch zecke/sysmobts-calibration created. 0.3.0-258-g8480fbf

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 created at 8480fbf803b410b3c7b67ce5f970a7a38f151a2e (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=8480fbf803b410b3c7b67ce5f970a7a… commit 8480fbf803b410b3c7b67ce5f970a7a38f151a2e 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=6d54dee99d578834fa177d9f2a049c7… commit 6d54dee99d578834fa177d9f2a049c752105f9c4 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=2419e9ab3bf4fe58a2652c8d0133f7a… commit 2419e9ab3bf4fe58a2652c8d0133f7ad0eb7e74a Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 17:33:09 2014 +0100 sysmobts: Add FD_WRITE to the event situation libosmo-abis doesn't reset the ->when flags when (re)connecting. This leads to not receiving a "ready to write" information on the socket, which in turns leads to ipa_client_fd_cb not being called and then updown_cb would only be called at a very late stage. Work around and manually set the when flag http://cgit.osmocom.org/osmo-bts/commit/?id=f1cf0c29fd5467dc2cc49d2bc1c7b2d… commit f1cf0c29fd5467dc2cc49d2bc1c7b2d42478c14f 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=97b0f8dc07ede7181eead1eba414771… commit 97b0f8dc07ede7181eead1eba414771e6af8452c 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. http://cgit.osmocom.org/osmo-bts/commit/?id=6c905943f93673ea5b5b21ac4ffcb54… commit 6c905943f93673ea5b5b21ac4ffcb549ac665d1c Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Dec 12 15:17:02 2014 +0100 sysmobts: Remove unused global variables We do not need to have these variables anymore. Just remove them. ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)