osmo-bts.git branch max/l1sap updated. 0.4.0-116-gff56df5

gitosis at osmocom.org gitosis at osmocom.org
Mon Feb 22 11:07:59 UTC 2016

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, max/l1sap has been updated
  discards  afcc88d095e13553c3e7a11cb454c4eb0a533945 (commit)
       via  ff56df575a44b6417614cab19b066f9c6dbf91a7 (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 (afcc88d095e13553c3e7a11cb454c4eb0a533945)
             N -- N -- N (ff56df575a44b6417614cab19b066f9c6dbf91a7)

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 ff56df575a44b6417614cab19b066f9c6dbf91a7
Author: Max <msuraev at sysmocom.de>
Date:   Thu Feb 18 17:48:07 2016 +0100

    Fix ocmo-bts-octphy interaction with OsmoPCU
    Previously osmo-bts-octphy have not provided in-band presence
    information which cause off-by-one errors and misinterpretation of
    ph_data_ind by PCU. This fixed now by adding support for explicitly
    passing PH-DATA presence info. Corresponding check and in-band passing
    of presence information are removed.
    Note: this requires libosmocore version with osmo_ph_pres_info_type
    support integrated.


Summary of changes:

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

More information about the osmocom-commitlog mailing list