From: gitosis@osmocom.org
Precedence: list
To: osmocom-commitlog@lists.osmocom.org
Date: Thu, 20 Jun 2013 15:50:30 GMT
Message-ID: <201306201550.r5KFoUk1097136@git.osmocom.org>
Subject: osmo-bts.git branch sysmocom/0.3.0-next updated. 0.3.0-7-g602afee
Message: 9

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, sysmocom/0.3.0-next has been updated
       via  602afee3df4cace9af26931b58afd0ca65103e0d (commit)
       via  026a716bc6e71c8f6b5a9d77115e2293f9262e28 (commit)
      from  d7b37b68cacc508fb2814013bfdbee081cd29efd (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=602afee3df4cace9af26931b58afd0ca65103e0d

commit 602afee3df4cace9af26931b58afd0ca65103e0d
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Thu Jun 20 17:18:38 2013 +0200

    sysmobts: Introduce an auto-band config to ease DCS/DCS, PCS/PCS changes
    
    During development one switches from GSM900 to GSM1800 and GSM850 to
    GSM1900. This commit attempts to make this switch more easy.
    
    GSM1800 and GSM1900 have overlapping ARFCNs. This means that the
    mapping from bands to arfcn is not injective. Because of that I
    removed the code to deduce the band from the ARFCN. This was done
    in commit 8c3d807b3fc785ffb18aeb97355150c92221e8a0. The auto-band
    option allows to move between GSM900/GSM1800 and GSM850/GSM1900.
    
    Add a simple testcase with these auto-band configurations.

http://cgit.osmocom.org/osmo-bts/commit/?id=026a716bc6e71c8f6b5a9d77115e2293f9262e28

commit 026a716bc6e71c8f6b5a9d77115e2293f9262e28
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Thu Jun 20 17:46:27 2013 +0200

    sysmobts: Do not write "trx-calibration-path (null)" in the config file
    
    When not specifying a config path, then saving the running config
    it would end up as "(null)" and then leads to an error like this:
    
     <0006> calib_file.c:147 Failed to open '(null)/calib_rxu_850.cfg' for calibration data.
    
    Add a NULL check to avoid this issue when writing the config file.

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

Summary of changes:
 .gitignore                             |   1 +
 configure.ac                           |   1 +
 include/osmo-bts/gsm_data.h            |   3 +
 src/osmo-bts-sysmo/Makefile.am         |   4 +-
 src/osmo-bts-sysmo/oml.c               |  19 +----
 src/osmo-bts-sysmo/sysmobts_vty.c      |  36 +++++++++-
 src/osmo-bts-sysmo/utils.c             |  87 +++++++++++++++++++++++
 src/osmo-bts-sysmo/utils.h             |  10 +++
 tests/Makefile.am                      |   2 +-
 tests/{paging => sysmobts}/Makefile.am |  11 +--
 tests/sysmobts/sysmobts_test.c         | 122 +++++++++++++++++++++++++++++++++
 tests/sysmobts/sysmobts_test.ok        |  19 +++++
 12 files changed, 287 insertions(+), 28 deletions(-)
 create mode 100644 src/osmo-bts-sysmo/utils.c
 create mode 100644 src/osmo-bts-sysmo/utils.h
 copy tests/{paging => sysmobts}/Makefile.am (54%)
 create mode 100644 tests/sysmobts/sysmobts_test.c
 create mode 100644 tests/sysmobts/sysmobts_test.ok


hooks/post-receive
-- 
Osmocom BTS-side code (Abis, scheduling, ...)


