osmo-trx.git branch fairwaves/pending updated. 8828b65e3feaf1dce3be382104655486e938aa5c

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.org
Tue Jun 9 03:16:09 UTC 2015


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, fairwaves/pending has been updated
       via  8828b65e3feaf1dce3be382104655486e938aa5c (commit)
       via  b594b120161861f03d7dfc15189e604a5677aa43 (commit)
       via  a96a0578134a5c719a25198e9790f2e84f356f0a (commit)
      from  37b445d4c8ecb06ab2bd5cd5aa582de4d74b8eba (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=8828b65e3feaf1dce3be382104655486e938aa5c

commit 8828b65e3feaf1dce3be382104655486e938aa5c
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date:   Mon Jun 8 23:14:42 2015 -0400

    Cheacking in a more relevant README.
    
    This one is from the OpenBTS's TRXManager and actually describes the transceiver
    API and behavior.

http://cgit.osmocom.org/osmo-trx/commit/?id=b594b120161861f03d7dfc15189e604a5677aa43

commit b594b120161861f03d7dfc15189e604a5677aa43
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date:   Mon Jun 8 23:14:18 2015 -0400

    Checking in clockdump.sh utility.

http://cgit.osmocom.org/osmo-trx/commit/?id=a96a0578134a5c719a25198e9790f2e84f356f0a

commit a96a0578134a5c719a25198e9790f2e84f356f0a
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date:   Mon Jun 8 22:46:38 2015 -0400

    Transceiver: Update noise level only when the timeslot is marked as IDLE.
    
    We can't rely on an assumption that if we can't decode a burst - it's noise.
    There are many rasons why we can't decode a burst even if it's well above the
    noise level. Just one example is a RACH burst which can be overlapped with
    another RACH burst up to a level both are completely unrecognizable. Another
    example is when a burst is destroyed by bad multi-path.

-----------------------------------------------------------------------

Summary of changes:
 README                         | 218 ++++++++++++++++-------------------------
 Transceiver52M/Transceiver.cpp |  39 +++++---
 Transceiver52M/Transceiver.h   |   2 +-
 clockdump.sh                   |   3 +
 4 files changed, 114 insertions(+), 148 deletions(-)
 create mode 100755 clockdump.sh


hooks/post-receive
-- 
OpenBTS' transceiver retro-fit



More information about the osmocom-commitlog mailing list