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 "OpenBTS' transceiver retro-fit". The branch, master has been updated via 934da48618c25b9cc53575a64f085c8df618b882 (commit) via 7c405a0c1f3a0fcce04c0ad4e2b66d802780ec0d (commit) from 4cafb0fa15a069c182a7f8dc77ef645061bee30e (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-trx/commit/?id=934da48618c25b9cc53575a64f085c8d... commit 934da48618c25b9cc53575a64f085c8df618b882 Author: Pau Espin Pedrol <pespin@sysmocom.de> Date: Tue Jul 4 16:25:20 2017 +0200 transceiver: Avoid sending clock indications when trx is not powered on Stop calling writeClockInterface() when receiving commands in Transceiver::driveControl, otherwise it fools osmo-bts-trx clock skew check because it is always sending a clock indication with the same fn when it issues any commands during the time in between CMD POWEROFF and RSP POWERON, because fn is not increased during that period. Also use mForceClockInterface flag to delay delivery of first IND CLOCK until we start serving frames, otherwise the first one is sent and only after a long period of time the next clock indications are sent, when the radio starts to process bursts. That makes osmo-bts-trx unhappy because it expects to receive an IND CLOCK aprox at least every 400 frames. This way also we send the first IND CLOCK after the RSP POWERON 0 response. Change-Id: I91b81a4d7627cec39c1814a39ed4be306681b874 ----------------------------------------------------------------------- Summary of changes: Transceiver52M/Transceiver.cpp | 31 ++++++++++++++----------------- Transceiver52M/Transceiver.h | 6 +++--- 2 files changed, 17 insertions(+), 20 deletions(-) hooks/post-receive -- OpenBTS' transceiver retro-fit