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 "The Open Source GSM Base Band stack".
The branch, master has been updated
via d49a748cbbf7d7b5bb77f3d906179da9b462e6d1 (commit)
via a4d255269a7d4e58d2ec0fbb42483495b8c247c9 (commit)
from 8b9d3170ff265c934f6271bd445ff5a6788ffffb (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/osmocom-bb/commit/?id=d49a748cbbf7d7b5bb77f3d906179da9b462e6d1
commit d49a748cbbf7d7b5bb77f3d906179da9b462e6d1
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date: Thu Dec 14 04:03:59 2017 +0700
common/l1ctl.c move TCH bit-ordering to the firmware
Previously, TCH frames coming from L1 were reordered to the RTP
format. Moreover, the implementation had a few problems:
- L1CTL is not the best place for such manipulations;
- payloads with other than FR codec were corrupted.
Let's use RTP-ordered payloads on the L1CTL interface,
performing TCH frame reordering at the firmware.
Please note, that actual FR reordering was moved to the firmware
as is, without any codec determination. This could be fixed in
a separate change.
Change-Id: I81ec8ed3c9e72a62b22c1720c299cdc68b733cf1
http://cgit.osmocom.org/osmocom-bb/commit/?id=a4d255269a7d4e58d2ec0fbb42483495b8c247c9
commit a4d255269a7d4e58d2ec0fbb42483495b8c247c9
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date: Sat Dec 16 17:52:31 2017 +0700
L1CTL/L1CTL_CRYPTO_REQ: add key length and channel info
Previously, the L1CTL_CRYPTO_REQ message contained only a ciphering
algorithm and actual Kc key to be used. The key length was
calculated manually using the MSGB API.
Let's avoid manual calculations here, as it may cause unexpected
behavior if the message structure is changed. Also, let's fill
the UL header with minimal information about a channel, which
is going to be encrypted.
Change-Id: I5fab079907c5276322d3ec2b46cab81f10c7ed09
-----------------------------------------------------------------------
Summary of changes:
include/l1ctl_proto.h | 1 +
src/host/layer23/include/osmocom/bb/common/l1ctl.h | 4 +-
src/host/layer23/src/common/l1ctl.c | 47 +++----------------
src/host/layer23/src/mobile/gsm48_rr.c | 12 +++--
src/target/firmware/Makefile | 3 +-
src/target/firmware/layer1/l23_api.c | 5 +--
src/target/firmware/layer1/prim_tch.c | 52 ++++++++++++++++++++++
7 files changed, 73 insertions(+), 51 deletions(-)
hooks/post-receive
--
The Open Source GSM Base Band stack