This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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=4ad75704747d9f369010897bd94e0c2b3e7ed514 commit 4ad75704747d9f369010897bd94e0c2b3e7ed514 Author: Harald Welte <laforge at 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=5bd6132c044b022d17f113f55d4778ce686a6259 commit 5bd6132c044b022d17f113f55d4778ce686a6259 Author: Harald Welte <laforge at 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=916d508bf6312acbc29a3e3575151b9bc7bc66d2 commit 916d508bf6312acbc29a3e3575151b9bc7bc66d2 Author: Harald Welte <laforge at 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=acefd0586e5d463b2e7a6a039131994bc12573fc commit acefd0586e5d463b2e7a6a039131994bc12573fc Author: Harald Welte <laforge at 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=c092f4e1ded65447061198ea1c57458becc71574 commit c092f4e1ded65447061198ea1c57458becc71574 Author: Harald Welte <laforge at 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=d5bbd8ccf79eaf13bc23cc71accbeb3ff638b6dd commit d5bbd8ccf79eaf13bc23cc71accbeb3ff638b6dd Author: Harald Welte <laforge at 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, ...)