osmo-bts.git branch master updated. 0.7.0-26-g4b4c2ec

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, master has been updated via 4b4c2ec4b324b94b0a4f6b4c36a68bfc60bfce3d (commit) from 62b575db671f2ae1856a058611f1b1304e5cad68 (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=4b4c2ec4b324b94b0a4f6b4c36a68bf… commit 4b4c2ec4b324b94b0a4f6b4c36a68bfc60bfce3d Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Dec 8 18:34:52 2017 +0100 bts-trx: Avoid enqueueing consecutive duplicate messages to TRX While debugging other protocol/timing issues between osmobts-trx and osmo-trx, I found that sometimes two consecutives "POWER OFF" commands are enqueued and sent to osmo-trx. There's no point in doing so, as the write queue already maintains state and retries the command until a RSP is received, then goes for the next one. With this change we hence improve timing response as we don't need to wait for the second command to be processed, and on top we get cleaner logs and simplified states which are easier to debug. Change-Id: Ib6a5e7bfac8bc5e1b372da6a1f801c07a3d5ebb7 ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-trx/trx_if.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)