30 Jul
2017
30 Jul
'17
6:46 p.m.
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 82987f7a7dd35451b75326b34e36c8f83289f6f6 (commit)
via d6da809d2fe35a00e03b0ae1422536245acd28be (commit)
from 69e0461674611425beefa4753d8743978259f19c (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=82987f7a7dd35451b75326b34e36c8f…
commit 82987f7a7dd35451b75326b34e36c8f83289f6f6
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Jul 30 16:38:18 2017 +0200
L1SAP: Print chan_nr and link_id always as hex
The RSL Channel ID is best read / interpreted as hex value, not as
decimal, primarily due to the fact that it is a bit-mask of various
fields.
Change-Id: I9b72a67407870b485e7f7e8a72fa1ad30fc8ed4d
http://cgit.osmocom.org/osmo-bts/commit/?id=d6da809d2fe35a00e03b0ae14225362…
commit d6da809d2fe35a00e03b0ae1422536245acd28be
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Jul 30 16:03:32 2017 +0200
TRX / VIRT-PHY: Make check for BCCH/CCCH more specific
In bts_model_l1sap_down() we want to identify BCCH/CCCH channel numbers,
but our check is a bit non-specific. Let's make the check more specific
to only cover the BCCH, Uplink CCCH and Downlink CCCH C-bits as defined
n 3GPP TS 08.58 Section 9.3.1
Change-Id: Ia20ab09b96c87c0dfbfaf98e5b2a8d36423fac67
-----------------------------------------------------------------------
Summary of changes:
src/common/l1sap.c | 16 ++++++++--------
src/osmo-bts-trx/l1_if.c | 4 ++--
src/osmo-bts-virtual/l1_if.c | 4 ++--
3 files changed, 12 insertions(+), 12 deletions(-)
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)