osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-pcu.git branch max/gsmtap2 deleted. 0.2-747-gb145fb7
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, max/gsmtap2 has been deleted was b145fb7d04bf7d17556918045b650081f37e3e9d ----------------------------------------------------------------------- b145fb7d04bf7d17556918045b650081f37e3e9d Add gsmtap support to generic bts ----------------------------------------------------------------------- hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch master updated. 0.2-747-g528ff39
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, master has been updated via 528ff3910f6f4455c6aee9794e05bd7d54bcc01f (commit) via 2efdf69734dc8d7f0953caad1563552f53c47b06 (commit) via 9d5580b6dd8069dbb5cdfa00b65f73978f580bcc (commit) from 4f8438a6cd0f34bb22493b13154e382983bbda01 (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=528ff3910f6f4455c6aee9794e05bd7… commit 528ff3910f6f4455c6aee9794e05bd7d54bcc01f Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:42:33 2016 +0100 Add gsmtap support to generic bts Instrument TX and RX functions dealing with regular BTS (without direct DSP access) to use GSMTAP. Previously only DSP-related functions were instrumented. http://cgit.osmocom.org/osmo-pcu/commit/?id=2efdf69734dc8d7f0953caad1563552… commit 2efdf69734dc8d7f0953caad1563552f53c47b06 Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:39:30 2016 +0100 Introduce --gsmtap-ip/-i option This option allows user to use custom IP address instead of default "localhost". Correspondingly gsmtap init moved from sysmoBTS-specific code up to "bts" struct level. This way it can be easier reused by other implementations. The lack of regressions was verified by checking following command on sysmoBTS: "./osmo-pcu -c osmo-pcu.cfg -r 1 -i 192.168.10.1" where 192.168.10.1 is the host which was running wireshark and netcat: "nc -u -l 192.168.10.1 -p 4729" to accept gsmtap flow. http://cgit.osmocom.org/osmo-pcu/commit/?id=9d5580b6dd8069dbb5cdfa00b65f739… commit 9d5580b6dd8069dbb5cdfa00b65f73978f580bcc Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:26:10 2016 +0100 Ignore files generated by cscope tool Signed-off-by: Max <msuraev(a)sysmocom.de> ----------------------------------------------------------------------- Summary of changes: .gitignore | 1 + src/bts.h | 2 ++ src/pcu_l1_if.cpp | 43 ++++++++++++++++++++++++++++++------------- src/pcu_main.cpp | 17 ++++++++++++++++- src/sysmo_l1_if.c | 6 ++---- 5 files changed, 51 insertions(+), 18 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch max/gsmtap2 updated. 0.2-747-gb145fb7
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, max/gsmtap2 has been updated discards 83f260fe8f6347ba7f7bb5f3e89d3032782dc74b (commit) via b145fb7d04bf7d17556918045b650081f37e3e9d (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 (83f260fe8f6347ba7f7bb5f3e89d3032782dc74b) \ N -- N -- N (b145fb7d04bf7d17556918045b650081f37e3e9d) 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-pcu/commit/?id=b145fb7d04bf7d17556918045b65008… commit b145fb7d04bf7d17556918045b650081f37e3e9d Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:42:33 2016 +0100 Add gsmtap support to generic bts Instrument TX and RX functions dealing with regular BTS (without direct DSP access) to use GSMTAP. Previously only DSP-related functions were instrumented. ----------------------------------------------------------------------- Summary of changes: src/pcu_l1_if.cpp | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch max/gsmtap2 updated. 0.2-747-g83f260f
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, max/gsmtap2 has been updated discards 9fede59c8072797f94c6780757fac4c84bf8a9c6 (commit) via 83f260fe8f6347ba7f7bb5f3e89d3032782dc74b (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 (9fede59c8072797f94c6780757fac4c84bf8a9c6) \ N -- N -- N (83f260fe8f6347ba7f7bb5f3e89d3032782dc74b) 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-pcu/commit/?id=83f260fe8f6347ba7f7bb5f3e89d303… commit 83f260fe8f6347ba7f7bb5f3e89d3032782dc74b Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:42:33 2016 +0100 Add gsmtap support to generic bts Instrument TX and RX functions dealing with regular BTS (without direct DSP access) to use GSMTAP. Previously only DSP-related functions were instrumented. ----------------------------------------------------------------------- Summary of changes: src/pcu_l1_if.cpp | 48 +++++++++++++++++++++++++----------------------- 1 file changed, 25 insertions(+), 23 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch max/gsmtap2 updated. 0.2-747-g9fede59
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, max/gsmtap2 has been updated discards 372a5474539f900b200cf0f2017b571270ae16f2 (commit) via 9fede59c8072797f94c6780757fac4c84bf8a9c6 (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 (372a5474539f900b200cf0f2017b571270ae16f2) \ N -- N -- N (9fede59c8072797f94c6780757fac4c84bf8a9c6) 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-pcu/commit/?id=9fede59c8072797f94c6780757fac4c… commit 9fede59c8072797f94c6780757fac4c84bf8a9c6 Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:42:33 2016 +0100 Add gsmtap support to generic bts Instrument TX and RX functions dealing with regular BTS (without direct DSP access) to use GSMTAP. Previously only DSP-related functions were instrumented. ----------------------------------------------------------------------- Summary of changes: src/pcu_l1_if.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch max/gsmtap2 updated. 0.2-747-g372a547
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 "UNNAMED PROJECT". The branch, max/gsmtap2 has been updated discards 1abca6c33d95c0bf360d4dfc1f0bb15b195c957a (commit) via 372a5474539f900b200cf0f2017b571270ae16f2 (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 (1abca6c33d95c0bf360d4dfc1f0bb15b195c957a) \ N -- N -- N (372a5474539f900b200cf0f2017b571270ae16f2) 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-pcu/commit/?id=372a5474539f900b200cf0f2017b571… commit 372a5474539f900b200cf0f2017b571270ae16f2 Author: Max <msuraev(a)sysmocom.de> Date: Mon Feb 22 11:42:33 2016 +0100 Add gsmtap support to generic bts Instrument TX and RX functions dealing with regular BTS (without direct DSP access) to use GSMTAP. Previously only DSP-related functions were instrumented. ----------------------------------------------------------------------- Summary of changes: src/pcu_l1_if.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-bts.git branch master updated. 0.4.0-116-gcb20c83
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 BTS-side code (Abis, scheduling, ...)". The branch, master has been updated discards 2c541c652d1524c9770849c65cef9b3d039008bf (commit) via cb20c83323da485ff392ccffa7ec75de8e2ffede (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 (2c541c652d1524c9770849c65cef9b3d039008bf) \ N -- N -- N (cb20c83323da485ff392ccffa7ec75de8e2ffede) 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-bts/commit/?id=cb20c83323da485ff392ccffa7ec75d… commit cb20c83323da485ff392ccffa7ec75de8e2ffede Author: Max <msuraev(a)sysmocom.de> Date: Thu Feb 18 17:48:07 2016 +0100 Fix ocmo-bts-octphy interaction with OsmoPCU Previously osmo-bts-octphy have not provided in-band presence information which cause off-by-one errors and misinterpretation of ph_data_ind by PCU. This fixed now by adding support for explicitly passing PH-DATA presence info. Corresponding check and in-band passing of presence information are removed. Note: this requires libosmocore version with osmo_ph_pres_info_type support integrated. [hfreyther/max: Remove + 1 from the decoded length] ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-bts.git branch master updated. 0.4.0-116-g2c541c6
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via 2c541c652d1524c9770849c65cef9b3d039008bf (commit) from 94bb3769f36c8b64c5dc196f02f22994543997d2 (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=2c541c652d1524c9770849c65cef9b3… commit 2c541c652d1524c9770849c65cef9b3d039008bf Author: Max <msuraev(a)sysmocom.de> Date: Thu Feb 18 17:48:07 2016 +0100 Fix ocmo-bts-octphy interaction with OsmoPCU Previously osmo-bts-octphy have not provided in-band presence information which cause off-by-one errors and misinterpretation of ph_data_ind by PCU. This fixed now by adding support for explicitly passing PH-DATA presence info. Corresponding check and in-band passing of presence information are removed. Note: this requires libosmocore version with osmo_ph_pres_info_type support integrated. [hfreyther/max: Remove + 1 from the decoded length, bump the protocol version even if the ABI change is coming from libosmocore but let us be explicity here] ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/pcuif_proto.h | 2 +- include/osmo-bts/scheduler_backend.h | 2 +- src/common/l1sap.c | 5 +++-- src/common/scheduler.c | 3 ++- src/osmo-bts-octphy/l1_if.c | 1 + src/osmo-bts-trx/scheduler_trx.c | 16 +++++++--------- 6 files changed, 15 insertions(+), 14 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

openbsc.git branch neels/nitb-bind created. 0.15.0-166-gc1b4206
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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, neels/nitb-bind has been created at c1b420615d0c5a1087e44f97762a0b0b4bf3cb27 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=c1b420615d0c5a1087e44f97762a0b0b… commit c1b420615d0c5a1087e44f97762a0b0b4bf3cb27 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Feb 22 13:43:37 2016 +0100 libosmo_abis_init: pass new IP bind addr param All callers pass it as NULL to use any interface as before. This will change for at least osmo-nitb soon. ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

libosmo-abis.git branch neels/bind created. 0.3.2-2-gf552853
by gitosis＠osmocom.org 22 Feb '16

22 Feb '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 A-bis protcol interface library". The branch, neels/bind has been created at f55285329851b54bd42605bd70af4d2f437270d3 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/libosmo-abis/commit/?id=f55285329851b54bd42605bd70a… commit f55285329851b54bd42605bd70af4d2f437270d3 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Feb 22 13:29:09 2016 +0100 ip: make bind address configurable Add bind address params to libosmo_abis_init(), e1inp_init(), e1inp_ipaccess_init(). Rename e1inp_ipaccess_init() to e1inp_ip_init(). In fact the whole ipaccess reference should be named just ip, as it is used for all BTS models using IP network interfaces, not just those from the ip.access vendor. I couldn't resist to rename this function I am touching, but am restraining myself from kicking off a renaming avalanche apart from that. Add a priv pointer to struct e1inp_driver in order to communicate the bind address parameter from e1inp_ip_init() to ipaccess_line_update(). Add static ip_bind_addr() to default to "0.0.0.0" if the e1inp_driver's priv is not set, and use that in ipaccess_line_update(). ----------------------------------------------------------------------- hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog