osmo-bts.git branch achemeris/ber updated. 0.3.0-252-gcae9fb7

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, achemeris/ber has been updated discards 4a545be0f9e09865bb3b4b04fb39ebc50a006386 (commit) discards 741364453c41442cd01579ae4264261482a7350d (commit) discards f6edb3349c63df3aa943cff35edfe781e4c3e8b6 (commit) discards 31fa15c2f01ba81f018f5f3dec61fb1b38aae624 (commit) via cae9fb70692d1f5f75aba93ce4f0ce3514dc249b (commit) via c5bb8e8a4e5174e608b8b67aa6d24190dc61bc1e (commit) via 71e5b1d6778118682aed88dae741380ab8350e62 (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 (4a545be0f9e09865bb3b4b04fb39ebc50a006386) \ N -- N -- N (cae9fb70692d1f5f75aba93ce4f0ce3514dc249b) 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=cae9fb70692d1f5f75aba93ce4f0ce3… commit cae9fb70692d1f5f75aba93ce4f0ce3514dc249b Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Thu Apr 9 13:24:15 2015 +0300 trx: More logging for voice frame decoding functions. http://cgit.osmocom.org/osmo-bts/commit/?id=c5bb8e8a4e5174e608b8b67aa6d2419… commit c5bb8e8a4e5174e608b8b67aa6d24190dc61bc1e Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Tue Apr 7 21:17:01 2015 +0300 tests: Update bursts_test to accommodate BER calculations. http://cgit.osmocom.org/osmo-bts/commit/?id=71e5b1d6778118682aed88dae741380… commit 71e5b1d6778118682aed88dae741380ab8350e62 Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Mon Apr 6 00:12:02 2015 +0300 trx: Implement BER calculations. A known issue with this code is that BER is not updated for lost TCH frames, because osmo-trx doesn't send any indication for them and we don't have a callback to handle this. Otherwise the code seem to work fine. ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-trx/gsm0503_coding.c | 88 +++++++++++++++++++++++++++++---------- src/osmo-bts-trx/l1_if.c | 32 ++++++++++---- src/osmo-bts-trx/l1_if.h | 6 ++- src/osmo-bts-trx/scheduler.c | 71 +++++++++++++++++-------------- 4 files changed, 133 insertions(+), 64 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)