osmocom-commitlog March 2018

osmocom-commitlog@lists.osmocom.org

1 participants
149 discussions

Start a nNew thread

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-2058-gd316b844
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

1 0

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-2057-geb3a1cde
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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/trx has been updated via eb3a1cde8c29f90044ba7a0a180f7c8dc835952f (commit) via 2136891b7bbdfbd62f28f63c8a16711d9562ec1c (commit) via a92fd3388cd7eac69e18938832be688c9a425613 (commit) from 5eae19098ac6e0563d3e176818ca6a6a4fb8656a (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/osmocom-bb/commit/?id=eb3a1cde8c29f90044ba7a0a180f7… commit eb3a1cde8c29f90044ba7a0a180f7c8dc835952f Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Fri Mar 9 14:20:41 2018 +0700 trxcon/l1ctl_link.c: allocate msgb after its length is read Change-Id: I2b941c5ed91097c4ed2d859634bbe89f44546061 http://cgit.osmocom.org/osmocom-bb/commit/?id=2136891b7bbdfbd62f28f63c8a167… commit 2136891b7bbdfbd62f28f63c8a16711d9562ec1c Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Fri Mar 9 06:34:04 2018 +0700 trxcon: clarify L1CTL message length field Each L1CTL message gets its own length pushed in front before sending. This isn't specified in the 'l1ctl_proto.h', but assumed in the code. Let's clarify this. Change-Id: I118d00613aeaf5ff0bad1188fa5f7450d4ca8122 http://cgit.osmocom.org/osmocom-bb/commit/?id=a92fd3388cd7eac69e18938832be6… commit a92fd3388cd7eac69e18938832be688c9a425613 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Thu Mar 8 20:51:52 2018 +0700 trxcon: use meaningful names for L1CTL messages There are two types of L1CTL messages: received and to be transmitted. Let's use proper names to indicate this. Change-Id: I7c17687579282fa389bca35dc7edbc3582e55701 ----------------------------------------------------------------------- Summary of changes: src/host/trxcon/l1ctl.c | 8 +++++++- src/host/trxcon/l1ctl_link.c | 26 ++++++++++++-------------- src/host/trxcon/l1ctl_link.h | 8 ++++++++ 3 files changed, 27 insertions(+), 15 deletions(-) hooks/post-receive -- The Open Source GSM Base Band stack

1 0

osmo-ci.git branch master updated. 07653276019511efe7e188a80c307225ac78230d
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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 "CI scripts". The branch, master has been updated via 07653276019511efe7e188a80c307225ac78230d (commit) from a45a34e9d05d6b11430b1c33810f795afd75fe58 (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-ci/commit/?id=07653276019511efe7e188a80c307225… commit 07653276019511efe7e188a80c307225ac78230d Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Mar 7 14:08:35 2018 +0100 osmocom-latest-packages.sh: Catch latest tags outside master branch Some projects, like osmo-trx, may have tags created in a non-master branch. Let's catch those too. Tested with several osmocom repositories. The ones showing different behaviour are osmo-trx (expected) and other repositories which have wrong or no tags and are anyway not used since there's no OBS build for them. Old cmdline is left of ==, new is right: artwork: ( == ) asn1c: ( == ) docker-playground: (debian-jessie-buildslave-0.1.0 == ) layer1-api: (superfemto_v3.8.1 == ) libasn1c: (0.9.28 == 0.9.28) libgtpnl: (1.1.0 == 1.1.0) libosmo-abis: (0.4.0 == 0.4.0) libosmocore: (0.10.2 == 0.10.2) libosmo-netif: (0.1.1 == 0.1.1) libosmo-sccp: (0.8.1 == 0.8.1) libsmpp34: (1.12.0 == 1.12.0) meta-telephony: ( == ) mncc-python: ( == ) octphy-2g-headers: (OCTSDR-OPENBSC-02.09.00-B1121 == ) openbsc: (1.0.0 == 1.0.0) osmo-bsc: (1.1.2 == 1.1.2) osmo-bts: (0.7.0 == 0.7.0) osmo-ci: ( == ) osmocom-bb: (osmocon_v0.0.0 == ) osmo-ggsn: (1.1.0 == 1.1.0) osmo-gsm-manuals: ( == v1) osmo-gsm-tester: ( == 0.1) osmo-gsm-tester-conf: ( == ) osmo-gsm-tester-sysmocom: ( == ) osmo-hlr: (0.1.0 == 0.1.0) osmo-iuh: (0.2.0 == 0.2.0) osmo-mgw: (1.2.0 == 1.2.0) osmo-msc: (1.1.2 == 1.1.2) osmo-pcu: (0.4.0 == 0.4.0) osmo-python-tests: ( == ) osmo-sgsn: (1.2.0 == 1.2.0) osmo-sip-connector: (1.1.0 == 1.1.0) osmo-trx: (0.2.0 == 0.3.0) pysim: ( == ) python-smpplib: ( == ) Change-Id: I3b521a194f0ae9fdfa358423e66f30c1316c23e8 ----------------------------------------------------------------------- Summary of changes: scripts/osmocom-latest-packages.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CI scripts

1 0

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-2054-g5eae1909
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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/trx has been updated via 5eae19098ac6e0563d3e176818ca6a6a4fb8656a (commit) via 4cf722364bdafd90d12984531e4ec8c8548d6579 (commit) from c00985bf99cd38cab7f50855866524a4a60d47dd (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/osmocom-bb/commit/?id=5eae19098ac6e0563d3e176818ca6… commit 5eae19098ac6e0563d3e176818ca6a6a4fb8656a Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Sun Mar 11 04:18:06 2018 +0700 trxcon/scheduler: transmit dummy frames on CBTX lchans If at the moment of transmission there are no frames in TX buffer, then either a dummy LAPDm frame (0x01, 0x03, 0x01, 0x2b ...) or a silence frame (depending on a codec in use) shall be transmitted. This is required for proper measurements on the BTS side. Change-Id: Ie590990f2274ea476678f6b2079f90eeadab6501 http://cgit.osmocom.org/osmocom-bb/commit/?id=4cf722364bdafd90d12984531e4ec… commit 4cf722364bdafd90d12984531e4ec8c8548d6579 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Sun Mar 11 03:19:33 2018 +0700 trxcon/scheduler: introduce a new CBTX lchan flag This new flag is intended to indicate that continuous burst transmission is assumed on particular logical channel. In other words, if a logical channel has this flag, but there is nothing to transmit in a TX buffer, then either a dummy LAPDm frame or a silence frame shall be sent. Change-Id: I25fcf9eeb787ffe5378d92532439e67d7d42fa65 ----------------------------------------------------------------------- Summary of changes: src/host/trxcon/sched_lchan_desc.c | 60 ++++++++++++------------- src/host/trxcon/sched_prim.c | 89 ++++++++++++++++++++++++++++++++++++++ src/host/trxcon/sched_trx.c | 13 ++++++ src/host/trxcon/sched_trx.h | 14 ++++++ src/host/trxcon/trxcon.c | 4 ++ 5 files changed, 150 insertions(+), 30 deletions(-) hooks/post-receive -- The Open Source GSM Base Band stack

1 0

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-2052-gc00985bf
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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/trx has been updated via c00985bf99cd38cab7f50855866524a4a60d47dd (commit) via 2778e4ef432c261cbeaeb344137c465adc8393dd (commit) via f06f31fdf7e0fc4fd2d4cb3a444855bfaafd59da (commit) via cbf818d4dcba53b226df8d36966482dc8b6d6ef4 (commit) from 7fd8ef2d3f3d296a6032745396d3af8e8e3d4da2 (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/osmocom-bb/commit/?id=c00985bf99cd38cab7f5085586652… commit c00985bf99cd38cab7f50855866524a4a60d47dd Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Sun Mar 11 03:16:40 2018 +0700 trxcon/sched_trx.h: clarify lchan flags meaning Change-Id: I51b663dd16e46a4523488c3d3000922a7c3640d1 http://cgit.osmocom.org/osmocom-bb/commit/?id=2778e4ef432c261cbeaeb344137c4… commit 2778e4ef432c261cbeaeb344137c465adc8393dd Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Sun Mar 11 04:20:57 2018 +0700 trxcon/sched_trx.c: fix: omit inactive logical channels The sched_frame_clck_cb() is responsible for UL burst transmission. Iterating over each timeslot, it chooses a proper lchan handler according to a current frame number and a multiframe layout in use, takes a L2 UL frame from a TX buffer, and finally calls the chosen handler in order to to encode and transmit a taken frame. A handler should be called only for activated logical channels... but for some long time, there was a bug, so each lchan was processed, including inactive ones. It's time to fix this. Change-Id: I33e3ecc14be3ae64dfd02789c7f0970c945582c9 http://cgit.osmocom.org/osmocom-bb/commit/?id=f06f31fdf7e0fc4fd2d4cb3a44485… commit f06f31fdf7e0fc4fd2d4cb3a444855bfaafd59da Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Fri Mar 9 15:33:59 2018 +0700 trxcon/sched_trx.c: fix: properly deallocate lchans The llist_for_each_entry_safe() should be used instead of the llist_for_each_entry(), because it's safe against removal of llist entry. Found using Valgrind's memcheck tool. Change-Id: I65234971ec152df038c5388da537a503060c215b http://cgit.osmocom.org/osmocom-bb/commit/?id=cbf818d4dcba53b226df8d3696648… commit cbf818d4dcba53b226df8d36966482dc8b6d6ef4 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Fri Mar 9 16:20:12 2018 +0700 trxcon/configure.ac: add --enable-sanitize option Change-Id: I099de726f9d67213c56d996039b4207f80a727c6 ----------------------------------------------------------------------- Summary of changes: src/host/trxcon/configure.ac | 11 +++++++++++ src/host/trxcon/sched_trx.c | 10 ++++++++-- src/host/trxcon/sched_trx.h | 4 +++- 3 files changed, 22 insertions(+), 3 deletions(-) hooks/post-receive -- The Open Source GSM Base Band stack

1 0

osmo-bts.git branch master updated. 0.7.0-152-g02d1fe8
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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 02d1fe87f0fdf4d9e08cde9f727f00e17343c20c (commit) from 29cd7a84089b4a29748a0c9723f539bc6005ad99 (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=02d1fe87f0fdf4d9e08cde9f727f00e… commit 02d1fe87f0fdf4d9e08cde9f727f00e17343c20c Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Wed Feb 21 00:38:05 2018 +0100 implement support for 3-digit MNC with leading zeros Record the mnc_3_digits flag from SI and pass on via the PCU interface. Instead of changing to e.g. osmo_plmn_id, add the flag separately, and instead of bool use a uint8_t, to not raise any struct packing issues and clarify the flag's size beyond any doubt. Bump the PCU interface version to 9. This is one part of the three identical pcuif_proto.h patches: - I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 (osmo-bts) - I787fed84a7b613158a5618dd5cffafe4e4927234 (osmo-pcu) - I78f30aef7aa224b2e9db54c3a844d8f520b3aee0 (osmo-bsc) Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore) Change-Id: I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/gsm_data.h | 3 ++- include/osmo-bts/pcuif_proto.h | 6 ++++-- src/common/pcu_sock.c | 15 +++++---------- 3 files changed, 11 insertions(+), 13 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-pcu.git branch master updated. 0.4.0-100-gbdc55fa
by gitosis＠osmocom.org 11 Mar '18

11 Mar '18

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 "UNNAMED PROJECT". The branch, master has been updated via bdc55fad62e333951a0eb1fc7b96aaaec16dd6ff (commit) from 8343b4adbbe9afd4294232429696ee9736ec1004 (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-pcu/commit/?id=bdc55fad62e333951a0eb1fc7b96aaa… commit bdc55fad62e333951a0eb1fc7b96aaaec16dd6ff Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Wed Feb 21 00:39:07 2018 +0100 implement support for 3-digit MNC with leading zeros Receive the mnc_3_digits flag from the PCU interface. Bump the PCU interface to 9. This is one part of the three identical pcuif_proto.h patches: - I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 (osmo-bts) - I787fed84a7b613158a5618dd5cffafe4e4927234 (osmo-pcu) - I78f30aef7aa224b2e9db54c3a844d8f520b3aee0 (osmo-bsc) Add 3-digit flags and use the new RAI and LAI API from libosmocore throughout the code base to be able to handle an MNC < 100 that has three digits (leading zeros). Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore), Ib7176b1d65a03b76f41f94bc9d3293a8a07d24c6 (libosmocore) Change-Id: I787fed84a7b613158a5618dd5cffafe4e4927234 ----------------------------------------------------------------------- Summary of changes: include/osmocom/pcu/pcuif_proto.h | 6 ++++-- src/gprs_bssgp_pcu.cpp | 15 +++++++++------ src/gprs_bssgp_pcu.h | 2 +- src/pcu_l1_if.cpp | 11 ++++++----- src/pcu_main.cpp | 6 +++++- tests/alloc/AllocTest.cpp | 1 + tests/alloc/MslotTest.cpp | 1 + tests/edge/EdgeTest.cpp | 1 + tests/emu/pcu_emu.cpp | 3 ++- tests/fn/FnTest.cpp | 1 + tests/llc/LlcTest.cpp | 1 + tests/ms/MsTest.cpp | 1 + tests/tbf/TbfTest.cpp | 11 ++++++----- tests/types/TypesTest.cpp | 1 + 14 files changed, 40 insertions(+), 21 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmocom-bb.git branch stumpf/virt-phy deleted. osmocon_v0.0.0-1781-gbdf22f10
by gitosis＠osmocom.org 10 Mar '18

10 Mar '18

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, stumpf/virt-phy has been deleted was bdf22f106290cbb48f6bbe0c3515c4270f2b581b ----------------------------------------------------------------------- bdf22f106290cbb48f6bbe0c3515c4270f2b581b VIRT-PHY: Configurable signal power reductions for multiple arfcns. ----------------------------------------------------------------------- hooks/post-receive -- The Open Source GSM Base Band stack

1 0

osmo-bts.git branch master updated. 0.7.0-151-g29cd7a8
by gitosis＠osmocom.org 10 Mar '18

10 Mar '18

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 29cd7a84089b4a29748a0c9723f539bc6005ad99 (commit) from 58a95ac799034fdb60ec277eb23bc3c411d7c5e6 (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=29cd7a84089b4a29748a0c9723f539b… commit 29cd7a84089b4a29748a0c9723f539bc6005ad99 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Mar 10 11:27:43 2018 +0100 sysmobts: Compatibility with older firmware versions When using a firmware version < 3.6, the call to l1if_mute_rf() returned an error, which caused an OML CHG ADM STATE NACK. Let's check if the l1if_mute_rf() call is an un-mute for all timeslots (which apparently we do always at start-up). If it is, then acknowledge it even if muting is not supported by earlier firmwares. I suppose the change causing this problem was introduced in: commit b26b8fc77692e851469f3e27b9aeaeff233ffd2e Author: Holger Hans Peter Freyther <zecke(a)selfish.org> Date: Tue Mar 4 15:03:59 2014 +0100 sysmobts: Do a RF mute at initialization when the RC is locked With the current change applied, we can run the BTS with earlier firmware versions than 3.6.0 again. Tested with 3.1 and 2.4 Change-Id: I1a29c1031d96e65a0111bc812a90f2dbaf2a5aa3 ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-sysmo/l1_if.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-bts.git branch master updated. 0.7.0-150-g58a95ac
by gitosis＠osmocom.org 10 Mar '18

10 Mar '18

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 58a95ac799034fdb60ec277eb23bc3c411d7c5e6 (commit) from c2045474b1b500a6cc38c00cc807978ce9e8c5e5 (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=58a95ac799034fdb60ec277eb23bc3c… commit 58a95ac799034fdb60ec277eb23bc3c411d7c5e6 Author: Harald Welte <laforge(a)gnumonks.org> Date: Fri Mar 9 22:15:53 2018 +0100 sysinfo.c: SI1 is optional; Send SI2 at TC=0 if no SI1 exists SI1 is only required if frequency hopping is used or if NCH is used. So it's optional. If OsmoBTS has no SI1 configured, it will transmit the empty SI1 buffer at TC=0, and as a result no valid SI will be broadcast at TC=0. Change-Id: I41ab885c00e943199b2e939e98f30e267ecffbee Closes: OS#3051 ----------------------------------------------------------------------- Summary of changes: src/common/sysinfo.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

← Newer
1
...
7
8
9
10
11
12
13
14
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog March 2018