osmo-bts.git branch master updated. 0.4.0-521-g9b97d0f

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
Sun Jul 2 07:02:45 UTC 2017


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  9b97d0f683bccd71b035ece1a6caebfc0f26d1b1 (commit)
      from  a38d34112fb46c90ec4cb12c597778e65cceaef8 (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=9b97d0f683bccd71b035ece1a6caebfc0f26d1b1

commit 9b97d0f683bccd71b035ece1a6caebfc0f26d1b1
Author: Harald Welte <laforge at gnumonks.org>
Date:   Sat Jun 24 16:50:00 2017 +0200

    TRX: permit transmission of all-zero loopback frames
    
    For some reason, osmo-bts-trx attempted to interpret/validate the
    contents of the downlink TCH block that it was about to transmit.  If
    such checks are made, they should clearly be in the common part above
    L1SAP, and not in the bts-model specific part.
    
    Also, having the checks in place didn't allow us to send an all-zero
    downlink block, as is required for detection of uplink FER in a loopback
    testing setup, e.g. with CMU-300.
    
    Change-Id: I6388de98e4a7e20843a1be88a58bba8d2c9aa0d5

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

Summary of changes:
 src/osmo-bts-trx/scheduler_trx.c | 35 +++++------------------------------
 1 file changed, 5 insertions(+), 30 deletions(-)


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



More information about the osmocom-commitlog mailing list