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 "UNNAMED PROJECT".
The branch, master has been updated
via d935d88a8c5dbc3bce5476545a785a7a35cfc2d3 (commit)
from e9a138e11111f509f988807bbdc5ca8cce2b3d3d (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=d935d88a8c5dbc3bce5476545a785a7a35cfc2d3
commit d935d88a8c5dbc3bce5476545a785a7a35cfc2d3
Author: Philipp <pmaier at sysmocom.de>
Date: Mon Nov 7 13:07:36 2016 +0100
BTS: accept also relative frame numbers with rach requst
The rach request contains a relative frame number (Fn % 42432),
while BTS::rcv_rach() accepts the full frame number only.
Since the BTS is always aware of the full frame number this is
not a problem. But for BSC co-located PCU schemes it is a problem
since the rach request only contains the relative frame number
as mentioned above.
The pcu continusly receives frame number updates with the GSM time
indication message. It is simple to re-calculate the full frame
number from that information.
This patch makes BTS::rcv_rach() compatible with relative frame
numbers, while not breaking the compatibility for full frame
numbers
Change-Id: Iaa182d8d29c6a0f5fa06064c2eb48b21b1ba2775
-----------------------------------------------------------------------
Summary of changes:
src/bts.cpp | 15 +++++++++++++++
tests/tbf/TbfTest.cpp | 5 ++++-
2 files changed, 19 insertions(+), 1 deletion(-)
hooks/post-receive
--
UNNAMED PROJECT