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, 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=b3a2a3e24f44adcc6660d33cc9684a8f24271e2e
commit b3a2a3e24f44adcc6660d33cc9684a8f24271e2e
Author: Harald Welte <laforge at 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=c2b4c668f3510b7b0baace749c5a310959010e90
commit c2b4c668f3510b7b0baace749c5a310959010e90
Author: Harald Welte <laforge at 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, ...)