osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-iuh.git branch osmocom/gerrit-test updated. 216225cde8a6c08b68a718326a9b83b1a8095d7d
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been updated discards 866840f0708689c9c1388d113ae31430c31cf8cf (commit) via 216225cde8a6c08b68a718326a9b83b1a8095d7d (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 (866840f0708689c9c1388d113ae31430c31cf8cf) \ N -- N -- N (216225cde8a6c08b68a718326a9b83b1a8095d7d) 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/osmo-iuh/commit/?id=216225cde8a6c08b68a718326a9b83b… commit 216225cde8a6c08b68a718326a9b83b1a8095d7d Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: fix, remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's sysmocom/iu branch. 'make regen' first, to generate the .c from asn1, needed by the build. Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch osmocom/gerrit-test updated. 866840f0708689c9c1388d113ae31430c31cf8cf
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been updated discards f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a (commit) via 866840f0708689c9c1388d113ae31430c31cf8cf (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 (f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a) \ N -- N -- N (866840f0708689c9c1388d113ae31430c31cf8cf) 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/osmo-iuh/commit/?id=866840f0708689c9c1388d113ae3143… commit 866840f0708689c9c1388d113ae31430c31cf8cf Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's sysmocom/iu branch. Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch osmocom/gerrit-test updated. f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been updated discards 8136734a91d20cdcbc7a23594dc8e3c383d0a63b (commit) via f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a (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 (8136734a91d20cdcbc7a23594dc8e3c383d0a63b) \ N -- N -- N (f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a) 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/osmo-iuh/commit/?id=f6e2583cff59b7fa9b2fbee985a0d9b… commit f6e2583cff59b7fa9b2fbee985a0d9b5fbd7fb3a Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's sysmocom/iu branch. Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch osmocom/gerrit-test updated. 8136734a91d20cdcbc7a23594dc8e3c383d0a63b
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been updated discards 3610412393deaa7c7aaf515ee730d1c9ee85c52c (commit) via 8136734a91d20cdcbc7a23594dc8e3c383d0a63b (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 (3610412393deaa7c7aaf515ee730d1c9ee85c52c) \ N -- N -- N (8136734a91d20cdcbc7a23594dc8e3c383d0a63b) 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/osmo-iuh/commit/?id=8136734a91d20cdcbc7a23594dc8e3c… commit 8136734a91d20cdcbc7a23594dc8e3c383d0a63b Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: remove code dup, drop unnecessary dep asn1c Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Drop build of asn1c, only libasn1c is needed. Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's sysmocom/iu branch. Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch osmocom/gerrit-test updated. 3610412393deaa7c7aaf515ee730d1c9ee85c52c
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been updated discards 7f539437f7de4e2d3347b86e43add549bf38b339 (commit) via 3610412393deaa7c7aaf515ee730d1c9ee85c52c (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 (7f539437f7de4e2d3347b86e43add549bf38b339) \ N -- N -- N (3610412393deaa7c7aaf515ee730d1c9ee85c52c) 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/osmo-iuh/commit/?id=3610412393deaa7c7aaf515ee730d1c… commit 3610412393deaa7c7aaf515ee730d1c9ee85c52c Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: remove code dup, drop unnecessary dep asn1c Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Drop build of asn1c, only libasn1c is needed. Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch osmocom/gerrit-test created. 7f539437f7de4e2d3347b86e43add549bf38b339
by gitosis＠osmocom.org 11 Jul '16

11 Jul '16

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 code for Iuh interface". The branch, osmocom/gerrit-test has been created at 7f539437f7de4e2d3347b86e43add549bf38b339 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-iuh/commit/?id=7f539437f7de4e2d3347b86e43add54… commit 7f539437f7de4e2d3347b86e43add549bf38b339 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Jul 11 17:10:49 2016 +0200 jenkins.sh: remove code dup and unnecessary dependencies Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64 ----------------------------------------------------------------------- hooks/post-receive -- Osmocom code for Iuh interface

1 0

libosmocore.git branch master updated. 0.9.0-199-g02a6672
by gitosis＠osmocom.org 10 Jul '16

10 Jul '16

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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via 02a66728856d6a111ef61eca2cc052df052579a9 (commit) from f3239113db910962a4ccac2f93d689a86450264f (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/libosmocore/commit/?id=02a66728856d6a111ef61eca2cc0… commit 02a66728856d6a111ef61eca2cc052df052579a9 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 10 15:13:51 2016 +0200 fsm: delete the timer when changing state In osmo_fsm_inst_state_chg(), we need to stop any not-yet-expired timer of the old state before transitioning into the new state. Change-Id: I2558f9a7027a877ea8263785ed3c8d70d2513996 ----------------------------------------------------------------------- Summary of changes: src/fsm.c | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

libosmocore.git branch master updated. 0.9.0-198-gf323911
by gitosis＠osmocom.org 10 Jul '16

10 Jul '16

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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via f3239113db910962a4ccac2f93d689a86450264f (commit) from 673018fed99aab80c3ac23c95f568ff0bf272f60 (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/libosmocore/commit/?id=f3239113db910962a4ccac2f93d6… commit f3239113db910962a4ccac2f93d689a86450264f Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 10 15:11:45 2016 +0200 fsm: talloc + copy the 'id' passed into a FSM The 'id' is used to generate the human-readable name of the FSM. However, when the FSM creates slave FSMs later, the caller-passed "ID" mgiht long be gone again (e.g. it was on stack memory). So let's copy the 'id' string to a chunk of dynamically-allocated memory at time of FSM start to ensure we have it later when creating child FSMs. Change-Id: Ib88a2c02c5c91f17b4ec1e9db57a06d6d66465fb ----------------------------------------------------------------------- Summary of changes: src/fsm.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

libosmocore.git branch master updated. 0.9.0-197-g673018f
by gitosis＠osmocom.org 10 Jul '16

10 Jul '16

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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via 673018fed99aab80c3ac23c95f568ff0bf272f60 (commit) from f5f773f0130e1f61b84636f7aeb6e17f5140fd25 (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/libosmocore/commit/?id=673018fed99aab80c3ac23c95f56… commit 673018fed99aab80c3ac23c95f568ff0bf272f60 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Jul 10 15:09:43 2016 +0200 fsm: call 'onenter' as last step of a state change This is useful to allow the user to terinate the fsm from the onenter() callback. Change-Id: Ia45a1f3279e702028250e10dc54b2d46a4039905 ----------------------------------------------------------------------- Summary of changes: src/fsm.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

openbsc.git branch laforge/om2000-fsm created. 0.15.0-333-gd058dde
by gitosis＠osmocom.org 10 Jul '16

10 Jul '16

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 OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, laforge/om2000-fsm has been created at d058dde994bf5a53a15d1ab8c85854a1d3c2a169 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=d058dde994bf5a53a15d1ab8c85854a1… commit d058dde994bf5a53a15d1ab8c85854a1d3c2a169 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Jul 9 22:20:57 2016 +0200 WIP: OM2000: Full state machine implementation using osmo_fsm Our existing OM2000 code for initializing all Managed Objects of a BTS at startup was never complete. Rather than trying to fix the old-style code, introudce a hierarchy of osmo_fsm's reflecting the full protocol hand-shake and sequence of bringing up the individual MO's. If this works out well, it mihgt make sense to convert the TS 12.21 OML code for other BTS models, too. Change-Id: I3e11b28ba22b8c227e0401e6207fdda5381dda8c http://cgit.osmocom.org/openbsc/commit/?id=f5a0d88547aa4471684afc92c7889e3a… commit f5a0d88547aa4471684afc92c7889e3a7bda10db Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Jul 4 17:13:57 2016 +0200 Attempt at extending dynamic PDCH support to Ericcson RBS2000 In Ericsson RBS2000, all PDCH's are dynamic, i.e. there is only one shared PCHAN type for TCH/F, TCH/H and PDCH. The PDCH needs to be activated with a RSL CHAN ACT with some proprietary coding of the Channel Number IE. Change-Id: I48089fcf8328d52f57e97b003790ffdeed766367 ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog