osmo-bts.git branch zecke/power-control updated. 0.3.0-251-g4513d56

gitosis at osmocom.org gitosis at osmocom.org
Thu Dec 11 13:38:37 UTC 2014

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, zecke/power-control has been updated
  discards  d9efedd7642b19e18876208f91f78926386cde27 (commit)
  discards  ee5681149eb5a87f54abb508b291e347ef1ac6c7 (commit)
  discards  f9dbf1034b728bc8afce9b3c652115cebbfd6ba2 (commit)
  discards  09401832365953469cdb708ec8d950295eeec896 (commit)
       via  4513d561eb6ff83095c230fedcf1e6179d61a364 (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 (d9efedd7642b19e18876208f91f78926386cde27)
             N -- N -- N (4513d561eb6ff83095c230fedcf1e6179d61a364)

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 -----------------------------------------------------------------

commit 4513d561eb6ff83095c230fedcf1e6179d61a364
Author: Holger Hans Peter Freyther <holger at moiji-mobile.com>
Date:   Sat Dec 6 20:30:52 2014 +0100

    sysmobts: Add a manual ms power level control
    Currently the DSP is instructed to achieve a given uplink
    power target but there are circumstances (e.g. EMV testing)
    where we need more control over it. The "manual/software/osmo"
    power control can only be implemented per TRX and not per
    lchan. Add a very very basic control that checks the MS Power
    used by the phone, the actual receive level and then adjust
    the power.
    The code doesn't take the history into account, if the phone
    can not reach the requested power level the code will be stuck
    (e.g. no timeout based on multiframes). It has a mode for a
    fixed power control but no way to set it yet.


Summary of changes:
 src/common/rsl.c           |  8 +++++---
 src/osmo-bts-sysmo/l1_if.c | 26 +++++++++++++-------------
 2 files changed, 18 insertions(+), 16 deletions(-)

Osmocom BTS-side code (Abis, scheduling, ...)

More information about the osmocom-commitlog mailing list