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, master has been updated
       via  9955cc4306f30c20cc372e72f7ed9999d3a57177 (commit)
       via  c2e3ff58bcd4203fb3426b99c986e71386fbd2b4 (commit)
      from  322cfc49427209e5b686e85c4e5f8eb08037819a (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 -----------------------------------------------------------------

commit 9955cc4306f30c20cc372e72f7ed9999d3a57177
Author: Max <>
Date:   Thu Feb 8 16:50:20 2018 +0100

    osmo-bts-trx: ignore frame offset error on startup
    Previously we always printed error on startup:
    l1sap.c:461 Invalid condition detected: Frame difference is 627202-0=627202 
> 1!
    This is expected and of little practical use. Let's suppress it
    by checking that FN was actually initialized.
    Change-Id: I4f7cf285e437db0e980e1a2a3ab48a7255945448

commit c2e3ff58bcd4203fb3426b99c986e71386fbd2b4
Author: Max <>
Date:   Thu Feb 8 16:42:48 2018 +0100

    osmo-bts-trx: init nbits to know value
    It seems like some of the functions invoked by _sched_dl_burst()
    do not sent nbits properly. This leads to a number of errors on
    trx_if.c:593 Tx burst length 65535 invalid
    It happens in conjunction with:
    Transceiver.cpp:382:pushRadioVector: dumping STALE burst in TRX->USRP 
    Let's fix this by initializing nbits to 0 to make sure those bursts
    are properly ignored.
    Change-Id: Iaf85826861163c185925de528c8347ab22779e30


Summary of changes:
 src/common/l1sap.c               | 7 ++++---
 src/osmo-bts-trx/scheduler_trx.c | 2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)

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

Reply via email to