osmocom-commitlog February 2018

osmocom-commitlog@lists.osmocom.org

1 participants
214 discussions

libosmocore.git branch master updated. 0.10.2-184-g38c902b7

by gitosis＠osmocom.org

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 38c902b7765c2c689a8dbed8e0f832c504d74845 (commit) from a57f90c80baaf6c668ec8bb0272327bcbdd63b12 (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=38c902b7765c2c689a8dbed8e0f8… commit 38c902b7765c2c689a8dbed8e0f832c504d74845 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Feb 27 17:30:08 2018 +0100 l1sap: Add fields for higher-precision timing offset values So far, we used quarter-bits across the L1SAP between the hardware/PHY specific part of OsmoBTS and the common part. In order to increase the resolution, let's add fields/members for 1/256th bit. In order to keep ABI and API compatibility, we use a union around the old and new values, so old code will still compile + work withe new libosmocore. Change-Id: Ibb58113c2819fe2d6d23ecbcfb8b3fce4055025d ----------------------------------------------------------------------- Summary of changes: include/osmocom/gsm/l1sap.h | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

6 years, 7 months

libosmo-netif.git branch pespin/jitterbuffer updated. 0.1.1-23-g9ba6c51

by gitosis＠osmocom.org

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 network interface library". The branch, pespin/jitterbuffer has been updated discards 2099de0f844b27dc75efbf03866af7151bce1202 (commit) discards f914452452fc152ec66189d7e1e263185c4678e8 (commit) discards 7cbfabc52557f729708fafc5344a2357d5e26240 (commit) discards 0d4fcd098025a49780870584589faa5b98e4210a (commit) discards a4ab705af59b2ee9c54650f40374c092372d8e0a (commit) discards 27ea0babecb89bc4692b5b1bb6821456032c109f (commit) discards 5d2d02f6f911d5da75857379ca012dcbb2a52524 (commit) discards 6a8c55e66534617610d8ddd518670a46994f61c7 (commit) discards dc88bcd95279968ea2da6fd54485e5e710c54876 (commit) discards 0685976f165bcea8945f73c6dd29a411bddf6aee (commit) via 9ba6c51dde13923f7144fb58a1ae281ce1aaab31 (commit) via bb411828e34a1e27468ce8778b3df8aed3169180 (commit) via ae0e28f4abff51d0b39d22b76c4d12684e1d94f8 (commit) via 9be1f9e66c11a041ae9de0296f54dee16d5b02d8 (commit) via abd613f44c69252de6eae5a3a1700176df42b10c (commit) via c03fc8c42652c1657e36ec5c8ff780c64f7fde56 (commit) via d4c12836cd58e411f55c590de071150727fe7fd4 (commit) via f0e388608efa9190abe09adf8368c1bd160ac133 (commit) via cb78f051ba9623cea0fed920173d281f5c213493 (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 (2099de0f844b27dc75efbf03866af7151bce1202) \ N -- N -- N (9ba6c51dde13923f7144fb58a1ae281ce1aaab31) 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/libosmo-netif/commit/?id=9ba6c51dde13923f7144fb58a1… commit 9ba6c51dde13923f7144fb58a1ae281ce1aaab31 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 26 18:09:36 2018 +0100 WIP Change-Id: If8378fc8dd9672475ef12f7351305f27e9b363b8 http://cgit.osmocom.org/libosmo-netif/commit/?id=bb411828e34a1e27468ce8778b… commit bb411828e34a1e27468ce8778b3df8aed3169180 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Jun 9 14:04:31 2017 +0200 jibuf: Estimate src clock skew Change-Id: Ifae633d53107417a8e2f9b0f200d2711db72d199 http://cgit.osmocom.org/libosmo-netif/commit/?id=ae0e28f4abff51d0b39d22b76c… commit ae0e28f4abff51d0b39d22b76c4d12684e1d94f8 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Sun Apr 23 19:22:15 2017 +0200 jibuf: re-sync clock out of sync timestamps Change-Id: I33556b33d7549654442d9bdd7f31128792506652 http://cgit.osmocom.org/libosmo-netif/commit/?id=9be1f9e66c11a041ae9de0296f… commit 9be1f9e66c11a041ae9de0296f54dee16d5b02d8 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 17:25:09 2017 +0200 jibuf: Take RTP marker into account Change-Id: Ie142acfb45650e0af775f58226fd191beaf8178e http://cgit.osmocom.org/libosmo-netif/commit/?id=abd613f44c69252de6eae5a3a1… commit abd613f44c69252de6eae5a3a1700176df42b10c Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Thu Jun 8 17:06:58 2017 +0200 tests: jibuf_tool: Add parameters to control size of buffer Change-Id: I8a7fa39985f8d197e24c32cab80299aba2d03087 http://cgit.osmocom.org/libosmo-netif/commit/?id=c03fc8c42652c1657e36ec5c8f… commit c03fc8c42652c1657e36ec5c8ff780c64f7fde56 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 18:58:00 2017 +0200 tests: jibuf_tool: Add OSMUX support Change-Id: I0f02da0329e6739ff340d31113161bb520b1b760 http://cgit.osmocom.org/libosmo-netif/commit/?id=d4c12836cd58e411f55c590de0… commit d4c12836cd58e411f55c590de071150727fe7fd4 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 13:30:10 2017 +0200 tests: jibuf_tool: Improve jibuf_test to read pcaps Change-Id: I7a13c823fb70e0adbc5fa0726fd66b15dc40014e Signed-off-by: Pau Espin Pedrol <pespin(a)sysmocom.de> http://cgit.osmocom.org/libosmo-netif/commit/?id=f0e388608efa9190abe09adf83… commit f0e388608efa9190abe09adf8368c1bd160ac133 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Feb 27 18:32:56 2018 +0100 tests: jitter_tool: Initial commit Change-Id: I92307c8b1483dd488339771462290aae0ae5689a http://cgit.osmocom.org/libosmo-netif/commit/?id=cb78f051ba9623cea0fed92017… commit cb78f051ba9623cea0fed920173d281f5c213493 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 12 19:36:47 2017 +0200 jibuf: Add initial implementation of Jitter Buffer Change-Id: I9688ba9c4d5b733b9f29d0f15f73750f9271ef55 ----------------------------------------------------------------------- Summary of changes: include/osmocom/netif/jibuf.h | 3 +- src/jibuf.c | 131 ++--- tests/Makefile.am | 14 +- tests/jibuf/jibuf_test.c | 819 ++++++++++++----------------- tests/jibuf/jibuf_test.ok | 300 +++++++++++ tests/jibuf/jibuf_test2.c | 506 ------------------ tests/jibuf/jibuf_test2.ok | 1 - tests/jibuf/{jibuf_test.c => jibuf_tool.c} | 22 +- tests/testsuite.at | 8 +- 9 files changed, 725 insertions(+), 1079 deletions(-) delete mode 100644 tests/jibuf/jibuf_test2.c delete mode 100644 tests/jibuf/jibuf_test2.ok copy tests/jibuf/{jibuf_test.c => jibuf_tool.c} (97%) hooks/post-receive -- Osmocom network interface library

6 years, 7 months

osmo-bts.git branch master updated. 0.7.0-125-gc092f4e

by gitosis＠osmocom.org

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 c092f4e1ded65447061198ea1c57458becc71574 (commit) via d5bbd8ccf79eaf13bc23cc71accbeb3ff638b6dd (commit) from b3a2a3e24f44adcc6660d33cc9684a8f24271e2e (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/gsm_data_shared.h | 4 +-- include/osmo-bts/scheduler.h | 6 ++-- include/osmo-bts/scheduler_backend.h | 12 +++---- src/common/l1sap.c | 2 +- src/common/measurement.c | 10 +++--- src/common/scheduler.c | 4 +-- src/osmo-bts-trx/l1_if.c | 12 +++---- src/osmo-bts-trx/l1_if.h | 2 +- src/osmo-bts-trx/loops.c | 31 +++++++++--------- src/osmo-bts-trx/loops.h | 2 +- src/osmo-bts-trx/scheduler_trx.c | 54 ++++++++++++++++---------------- src/osmo-bts-trx/trx_if.c | 12 +++---- src/osmo-bts-virtual/scheduler_virtbts.c | 10 +++--- 13 files changed, 82 insertions(+), 79 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

6 years, 7 months

osmo-bts.git branch laforge/meas256 created. 0.7.0-129-g4ad7570

by gitosis＠osmocom.org

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, laforge/meas256 has been created at 4ad75704747d9f369010897bd94e0c2b3e7ed514 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=4ad75704747d9f369010897bd94e0c2… commit 4ad75704747d9f369010897bd94e0c2b3e7ed514 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Feb 21 22:30:23 2018 +0100 WIP: FIX REL_IND merge mismatch Change-Id: I823c9101bcca72d5792e16379b02d3602ffc2726 http://cgit.osmocom.org/osmo-bts/commit/?id=5bd6132c044b022d17f113f55d4778c… commit 5bd6132c044b022d17f113f55d4778ce686a6259 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Feb 27 19:41:11 2018 +0100 Add high-accuracy ToA value to Uplink Measurement Reports Normal Abis RSL MEasurement Results contain only the "MS Timing Offset IE" in units of full symbols. In some use cases it is important to have higher-accuracy timing information exposed to the BSC. We do this by adding the average timing offset value during the last measurement interval in 1/256th symbol accuracy to the "Supplementary MEasuremen Information" part of the TS 48.058 9.3.25 Uplink Measurements IE. In order to avoid any compatibility issues, this feature is only enabled if the new vty config command "supp-meas-info toa256" at the bts node is enabled. Change-Id: Ie85e53b47d4041cc4e6d7b78406ae8b79b2d9397 http://cgit.osmocom.org/osmo-bts/commit/?id=916d508bf6312acbc29a3e3575151b9… commit 916d508bf6312acbc29a3e3575151b9bc7bc66d2 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Feb 27 19:39:24 2018 +0100 measurement: Keep average of high-accurate ToA value in lchan At the end of a measurement processing window, we currently compute the ToA / timing offset at 1/256th symbol accuracy, but we only print it to the log. Let's store the value in the lchan to make it usable by other code in follow-up patches. Change-Id: I5f00a16ac966b627d9452a98b8fa70984bed684a http://cgit.osmocom.org/osmo-bts/commit/?id=acefd0586e5d463b2e7a6a039131994… commit acefd0586e5d463b2e7a6a039131994bc12573fc Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Feb 27 16:58:46 2018 +0100 L1SAP: Increase resolution of reported burst timing Before this patch we had: * osmo-bts-trx internally using 1/256th bit/symbol period * osmo-bts-sysmo internally using 1/4 bit/smbol period * PCU interface using 1/4 * L1SAP interface using 1/4 * measurement processing code on top of L1SAP using 1/256 So for sysmo/lc15/octphy we are not loosing resolution, but for osmo-bts-trx we're arbitrarily reducing the resolution via L1SAP only then to compute with higher resolution again. Let's change L1SAP to use 1/256 bits and hence not loose any resolution. This requires a corresponding change in libosmocore for l1sap.h, which is found in Change-Id Ibb58113c2819fe2d6d23ecbcfb8b3fce4055025d Change-Id: If9b0f617845ba6c4aa47969f521734388197c9a7 http://cgit.osmocom.org/osmo-bts/commit/?id=c092f4e1ded65447061198ea1c57458… commit c092f4e1ded65447061198ea1c57458becc71574 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Feb 21 12:41:02 2018 +0100 measurement.c: higher-precision TA/TOA math Change-Id: I0dc8e78545465dfc5c93691a49b86b6b8b56b432 http://cgit.osmocom.org/osmo-bts/commit/?id=d5bbd8ccf79eaf13bc23cc71accbeb3… commit d5bbd8ccf79eaf13bc23cc71accbeb3ff638b6dd Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Feb 19 14:21:36 2018 +0100 trx/scheduler: Use integer math for TOA (Timing of Arrival) There's no need to express TOA as a float: * We receive it as signed 16bit integer in units 1/256 symbol periods * We pass it to L1SAP as signed integer in 1/4 symbol periods So turn it into an int16_t with 1/256 symbol period accuracy throughout the code to avoid both float arithmetic as well as loosing any precision. Change-Id: Idce4178e0b1f7e940ebc22b3e2f340fcd544d4ec ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

6 years, 7 months

osmo-bts.git branch master updated. 0.7.0-123-gb3a2a3e

by gitosis＠osmocom.org

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 b3a2a3e24f44adcc6660d33cc9684a8f24271e2e (commit) via c2b4c668f3510b7b0baace749c5a310959010e90 (commit) from b60d9e9464dabba64e7ba73a1a8f41adab21ff31 (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=b3a2a3e24f44adcc6660d33cc9684a8… commit b3a2a3e24f44adcc6660d33cc9684a8f24271e2e Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Jun 27 18:56:01 2016 +0200 RACH decoding: Use BER threshold for RACH ghost detection When decoding RACH bursts, we should use a BER threshold in order to help distinguish 'ghost' RACH bursts from real RACH bursts. The theoretical ideal threshold according to some papers is 7 out of 41 bits qhich aquals to Eb/N0 of 0 dB = 0.1707 (17.07%) We add a new 'ber10k' parameter to the RACH indication l1sap primitive (needs separate change for libosmocore), and then fill this value from osmo-bts-{sysmo,lc15,trx,octphy}. The common part above L1SAP then applies the threshold, which can be changed from vty using the "max-ber10k-rach <0-10000>" command available at the BTS node. The unit is BER in 1/10000, i.e. a value of 100 equals 1% bit error rate. Change-Id: Ic41c11f6312a36baa2738547e8dcec80829457f8 http://cgit.osmocom.org/osmo-bts/commit/?id=c2b4c668f3510b7b0baace749c5a310… commit c2b4c668f3510b7b0baace749c5a310959010e90 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Feb 26 11:57:49 2018 +0100 Move rach_busy counting above L1SAP In the past, rach_busy counting was performed below L1SAP, while reporting was handled above. This lead to subtle differences between the BTS models, such as osmo-bts-trx missing to increment rach_busy. Let's move the rach_busy counting above L1SAP to share more code. This means we need libosmocore Change-Id I9439810c3a3ad89ea0302753617b850749af887c for the additional required parameters in ph_rach_ind_param, as well as libosmocore Change-id I2b1926a37bde860dcfeb0d613eb55a71271928c5 for osmo-bts-trx to determine the RACH bit error rate. Change-Id: I3b989580cb38082e3fd8fc50a11fedda13991092 Closes: OS#3003 ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/gsm_data.h | 1 + src/common/bts.c | 1 + src/common/l1sap.c | 27 +++++++++++++++++++++------ src/common/vty.c | 16 ++++++++++++++++ src/osmo-bts-litecell15/l1_if.c | 16 ++++++---------- src/osmo-bts-octphy/l1_if.c | 32 +++++++++++--------------------- src/osmo-bts-sysmo/l1_if.c | 16 ++++++---------- src/osmo-bts-trx/scheduler_trx.c | 6 +++++- 8 files changed, 67 insertions(+), 48 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

6 years, 7 months

osmo-bts.git branch master updated. 0.7.0-121-gb60d9e9

by gitosis＠osmocom.org

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 b60d9e9464dabba64e7ba73a1a8f41adab21ff31 (commit) from 0d6c3e811007be828207c0f69ff4e2dddeeb64db (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=b60d9e9464dabba64e7ba73a1a8f41a… commit b60d9e9464dabba64e7ba73a1a8f41adab21ff31 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Feb 26 22:31:56 2018 +0100 scheduler: Add missing \n at end of LOG statement Change-Id: I55419dfa884b4170dfed696a7e1334940a46ba82 ----------------------------------------------------------------------- Summary of changes: src/common/scheduler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

6 years, 7 months

libosmocore.git branch master updated. 0.10.2-183-ga57f90c8

by gitosis＠osmocom.org

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 a57f90c80baaf6c668ec8bb0272327bcbdd63b12 (commit) from 726ba36201226fe1b0e768b27cb67bce45443df5 (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=a57f90c80baaf6c668ec8bb02723… commit a57f90c80baaf6c668ec8bb0272327bcbdd63b12 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Feb 26 11:49:59 2018 +0100 l1sap: Add RSSI, BER and quarter-bit accurate timing to PH-RACH.ind Let's extend PH-RACH.ind with some useful data across the L1SAP boundary. Change-Id: I9439810c3a3ad89ea0302753617b850749af887c Related: OS#3003 ----------------------------------------------------------------------- Summary of changes: include/osmocom/gsm/l1sap.h | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- An utility library for Open Source Mobile Communications

6 years, 7 months

libosmo-netif.git branch pespin/jitterbuffer updated. 0.1.1-24-g2099de0

by gitosis＠osmocom.org

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 network interface library". The branch, pespin/jitterbuffer has been updated discards cde6815efa38616be3bca3b16386a1e7e9ff3770 (commit) discards e245cdfb04a9b382f0943ffa7e29a9eea4d325dd (commit) discards 8283292c4b01da2d893aafc844c9dfa123a39381 (commit) discards b55e6ca74825c4ecacd11ec21d57959c6e4bcbbe (commit) discards 12131da94cf3fcb6f562be513ba3381152411afc (commit) discards 8e39adfed8e5b0a6786827a8323b37fa0397d426 (commit) discards 84ec6cfde314c76a227e72dfaca0abc77f3b7be9 (commit) discards 350120cda3201e84a9626d71b6846dbd0aef1b55 (commit) discards e7b2a8f4eab92fc95d1368fe4acd61a24face5b3 (commit) via 2099de0f844b27dc75efbf03866af7151bce1202 (commit) via f914452452fc152ec66189d7e1e263185c4678e8 (commit) via 7cbfabc52557f729708fafc5344a2357d5e26240 (commit) via 0d4fcd098025a49780870584589faa5b98e4210a (commit) via a4ab705af59b2ee9c54650f40374c092372d8e0a (commit) via 27ea0babecb89bc4692b5b1bb6821456032c109f (commit) via 5d2d02f6f911d5da75857379ca012dcbb2a52524 (commit) via 6a8c55e66534617610d8ddd518670a46994f61c7 (commit) via dc88bcd95279968ea2da6fd54485e5e710c54876 (commit) via 0685976f165bcea8945f73c6dd29a411bddf6aee (commit) via 525256a15a581daec7afd9edd65f10b827ff2f51 (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 (cde6815efa38616be3bca3b16386a1e7e9ff3770) \ N -- N -- N (2099de0f844b27dc75efbf03866af7151bce1202) 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/libosmo-netif/commit/?id=2099de0f844b27dc75efbf0386… commit 2099de0f844b27dc75efbf03866af7151bce1202 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Feb 27 17:34:29 2018 +0100 Add jibuf_test2 Change-Id: Ie0f894b3638fa20ff7487f15ce46fc5a51a39680 http://cgit.osmocom.org/libosmo-netif/commit/?id=f914452452fc152ec66189d7e1… commit f914452452fc152ec66189d7e1e263185c4678e8 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 26 18:09:36 2018 +0100 WIP Change-Id: If8378fc8dd9672475ef12f7351305f27e9b363b8 http://cgit.osmocom.org/libosmo-netif/commit/?id=7cbfabc52557f729708fafc534… commit 7cbfabc52557f729708fafc5344a2357d5e26240 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Jun 9 14:04:31 2017 +0200 jibuf: Estimate src clock skew Change-Id: Ifae633d53107417a8e2f9b0f200d2711db72d199 http://cgit.osmocom.org/libosmo-netif/commit/?id=0d4fcd098025a4978087058458… commit 0d4fcd098025a49780870584589faa5b98e4210a Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Thu Jun 8 17:06:58 2017 +0200 tests: jibuf_test: Add parameters to control size of buffer Change-Id: I8a7fa39985f8d197e24c32cab80299aba2d03087 http://cgit.osmocom.org/libosmo-netif/commit/?id=a4ab705af59b2ee9c54650f403… commit a4ab705af59b2ee9c54650f40374c092372d8e0a Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Sun Apr 23 19:22:15 2017 +0200 jibuf: re-sync clock out of sync timestamps Change-Id: I33556b33d7549654442d9bdd7f31128792506652 http://cgit.osmocom.org/libosmo-netif/commit/?id=27ea0babecb89bc4692b5b1bb6… commit 27ea0babecb89bc4692b5b1bb6821456032c109f Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 17:25:09 2017 +0200 jibuf: Take RTP marker into account Change-Id: Ie142acfb45650e0af775f58226fd191beaf8178e http://cgit.osmocom.org/libosmo-netif/commit/?id=5d2d02f6f911d5da75857379ca… commit 5d2d02f6f911d5da75857379ca012dcbb2a52524 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 18:58:00 2017 +0200 tests: jibuf_test: Add OSMUX support Change-Id: I0f02da0329e6739ff340d31113161bb520b1b760 http://cgit.osmocom.org/libosmo-netif/commit/?id=6a8c55e66534617610d8ddd518… commit 6a8c55e66534617610d8ddd518670a46994f61c7 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 13:30:10 2017 +0200 tests: jibuf: Improve jibuf_test to read pcaps Change-Id: I7a13c823fb70e0adbc5fa0726fd66b15dc40014e Signed-off-by: Pau Espin Pedrol <pespin(a)sysmocom.de> http://cgit.osmocom.org/libosmo-netif/commit/?id=dc88bcd95279968ea2da6fd544… commit dc88bcd95279968ea2da6fd54485e5e710c54876 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 19 17:20:34 2017 +0200 jibuf: Add osmo_jibuf_empty API This is useful to know if we need to keep iterating over osmo_select_main() to dequeue packets before finishing. Change-Id: I91a23e220c56924b847265c5dc752f286b109c2c http://cgit.osmocom.org/libosmo-netif/commit/?id=0685976f165bcea8945f73c6dd… commit 0685976f165bcea8945f73c6dd29a411bddf6aee Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Apr 12 19:36:47 2017 +0200 jibuf: Add initial implementation of Jitter Buffer Change-Id: I9688ba9c4d5b733b9f29d0f15f73750f9271ef55 http://cgit.osmocom.org/libosmo-netif/commit/?id=525256a15a581daec7afd9edd6… commit 525256a15a581daec7afd9edd65f10b827ff2f51 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 26 18:17:11 2018 +0100 test: osmo-pcap-test: Fix clock drift while replaying pcap file In the previous implementation, the processing time was not being taken into account, which was implicitly added for each new packet to be sent, which caused a steady incremental drift in the clock clearly visible when analysing a RTP stream. As it uses timespecsub, it depends on libosmocore Change-Id I45fc993b9bb0a343763238bf463c8640f47b00f1. Change-Id: I11cb9a63e16e829ccd4af1096b9f473c802d822f ----------------------------------------------------------------------- Summary of changes: src/jibuf.c | 10 +- tests/Makefile.am | 5 +- tests/jibuf/jibuf_test.c | 2 +- tests/jibuf/jibuf_test2.c | 506 ++++++++++++++++++++++++++ tests/jibuf/{jibuf_test.ok => jibuf_test2.ok} | 0 tests/jibuf/jitter.plt | 1 - tests/jibuf/{jitter.plt => seq.plt} | 10 +- tests/osmo-pcap-test/osmo_pcap.h | 4 +- tests/osmo-pcap-test/pcap.c | 29 +- tests/testsuite.at | 8 +- 10 files changed, 550 insertions(+), 25 deletions(-) create mode 100644 tests/jibuf/jibuf_test2.c copy tests/jibuf/{jibuf_test.ok => jibuf_test2.ok} (100%) copy tests/jibuf/{jitter.plt => seq.plt} (79%) hooks/post-receive -- Osmocom network interface library

6 years, 7 months

libosmocore.git branch master updated. 0.10.2-182-g726ba362

by gitosis＠osmocom.org

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 726ba36201226fe1b0e768b27cb67bce45443df5 (commit) from cc81722736c9bd2a0a16cf2247eda6b82074a198 (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=726ba36201226fe1b0e768b27cb6… commit 726ba36201226fe1b0e768b27cb67bce45443df5 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Mon Feb 26 18:03:44 2018 +0100 core: Add timespec helper macros and make timer_compat.h public If a monotonic clock must be used, then the clock_gettime API is used which uses timespec structures. Linux systems by default don't provide helpers to calculate time using timespecs, so let's add them here. Let's also make this header public so these helpers can be used in other projects using libosmocore (expected user: libosmo-netif). Change-Id: I45fc993b9bb0a343763238bf463c8640f47b00f1 ----------------------------------------------------------------------- Summary of changes: include/Makefile.am | 2 +- include/osmocom/core/timer_compat.h | 44 +++++++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

6 years, 7 months

osmo-pcu.git branch neels/mnc3 updated. 0.4.0-98-gdd1a661

by gitosis＠osmocom.org

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, neels/mnc3 has been updated discards c0391519d1e211cdb457c868088186991bcc1bb8 (commit) via dd1a661c034b9b15c60a7039c3601e0d00b5f173 (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 (c0391519d1e211cdb457c868088186991bcc1bb8) \ N -- N -- N (dd1a661c034b9b15c60a7039c3601e0d00b5f173) 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=dd1a661c034b9b15c60a7039c3601e0… commit dd1a661c034b9b15c60a7039c3601e0d00b5f173 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 version from 7 to 9 to match osmo-bts (see I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 there). 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), I49cd762c3c9d7ee6a82451bdf3ffa2a060767947 (osmo-bts) Change-Id: I787fed84a7b613158a5618dd5cffafe4e4927234 ----------------------------------------------------------------------- Summary of changes: src/pcu_main.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

6 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog February 2018