osmocom-bb.git branch fixeria/fake_trx updated. osmocon_v0.0.0-1839-g5d44a4a4

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
Sat Jul 15 16:41:51 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 "The Open Source GSM Base Band stack".

The branch, fixeria/fake_trx has been updated
  discards  7be84af24940e49fd2f356cc9c70c533cde86320 (commit)
  discards  4a8b0877e01541e23499c1c29646f241dd7fe593 (commit)
       via  5d44a4a40936716211aaa076555037e6f36078e8 (commit)
       via  f08e4191a5c4b848e95c5e68ee57cf975282747f (commit)
       via  926dd12390c1da4d7c03aa87ee98ae3446e6763e (commit)
       via  1412f60fe3e4fd33d2fe76ccecb5907a07b0a04a (commit)
       via  27a444fd93d7867e4f796d341da9fd2378431629 (commit)
       via  ce399fa1f2ee21b67e39ad523473172a1144df6c (commit)
       via  b9c472e12853f028194f2db5e0efa8331bbed288 (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 (7be84af24940e49fd2f356cc9c70c533cde86320)
            \
             N -- N -- N (5d44a4a40936716211aaa076555037e6f36078e8)

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 -----------------------------------------------------------------
http://cgit.osmocom.org/osmocom-bb/commit/?id=5d44a4a40936716211aaa076555037e6f36078e8

commit 5d44a4a40936716211aaa076555037e6f36078e8
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Sat Jul 15 22:51:12 2017 +0700

    host/trxcon/l1ctl.c: handle L1CTL_DATA_REQ
    
    Change-Id: Ia72fd3d55c86697ff144446bbae94f76839eb5a1

http://cgit.osmocom.org/osmocom-bb/commit/?id=f08e4191a5c4b848e95c5e68ee57cf975282747f

commit f08e4191a5c4b848e95c5e68ee57cf975282747f
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Sat Jul 15 22:46:54 2017 +0700

    host/trxcon/scheduler: implement xCCH TX capability
    
    Change-Id: I4da4816dcecc55eb9b4d2d6c631967026a5e4f68

http://cgit.osmocom.org/osmocom-bb/commit/?id=926dd12390c1da4d7c03aa87ee98ae3446e6763e

commit 926dd12390c1da4d7c03aa87ee98ae3446e6763e
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Sat Jul 15 15:20:35 2017 +0700

    host/trxcon/l1ctl.c: handle L1CTL_DM_{EST,REL}_REQ
    
    Change-Id: Ifdf229a6dd3c73ede313d2bfe384032e3887cc3a

http://cgit.osmocom.org/osmocom-bb/commit/?id=1412f60fe3e4fd33d2fe76ccecb5907a07b0a04a

commit 1412f60fe3e4fd33d2fe76ccecb5907a07b0a04a
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Jul 14 18:33:48 2017 +0700

    host/trxcon/scheduler: fix TS index in sched_trx_configure_ts()
    
    TS index was not assigned after allocation of a new one.
    
    Change-Id: I1b62218f863acf27fb1d1f46b273b345b97d33d8

http://cgit.osmocom.org/osmocom-bb/commit/?id=27a444fd93d7867e4f796d341da9fd2378431629

commit 27a444fd93d7867e4f796d341da9fd2378431629
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Jul 14 10:46:23 2017 +0700

    host/trxcon/l1ctl.c: implement FBSB expire timer
    
    Change-Id: I27f96cbe951de164fcecaf19f8305db5e5b20229

http://cgit.osmocom.org/osmocom-bb/commit/?id=ce399fa1f2ee21b67e39ad523473172a1144df6c

commit ce399fa1f2ee21b67e39ad523473172a1144df6c
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Jul 14 19:15:41 2017 +0700

    host/trxcon/l1ctl.c: fix L1CTL_RACH_{REQ,CONF} handling
    
    Previously, L1CTL_RACH_REQ / L1CTL_RACH_CONF messages were
    handled without l1ctl_info_ul / l1ctl_info_dl header, what
    caused incorrect data parsing.
    
    Change-Id: I145d137f2cc7de234965e4fe64d9367ed6ccb999

http://cgit.osmocom.org/osmocom-bb/commit/?id=b9c472e12853f028194f2db5e0efa8331bbed288

commit b9c472e12853f028194f2db5e0efa8331bbed288
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Fri Jul 14 10:28:26 2017 +0700

    host/trxcon/l1ctl.c: fix incomplete msg in l1ctl_tx_fbsb_conf()
    
    Previously, all L1CTL_FBSB_CONF messages were sent without
    required l1ctl_info_dl header, what caused unpredictable
    behavior on higher layers (L2 & L3). Let's fix it.
    
    Change-Id: I8dae597bb4c09df36f80944434ce3624569f2cf8

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

Summary of changes:
 src/host/trxcon/l1ctl.c                | 185 +++++++++++++++++++++++++++++++--
 src/host/trxcon/l1ctl.h                |   2 +-
 src/host/trxcon/sched_lchan_desc.c     |   5 +-
 src/host/trxcon/sched_lchan_handlers.c |  91 +++++++++++++++-
 src/host/trxcon/sched_trx.c            |  51 +++++++++
 src/host/trxcon/sched_trx.h            |   5 +
 src/host/trxcon/trx_if.h               |   1 +
 7 files changed, 328 insertions(+), 12 deletions(-)


hooks/post-receive
-- 
The Open Source GSM Base Band stack



More information about the osmocom-commitlog mailing list