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 a7bfb6c8dabcba6fb3534c4733d88fb9e466ae15 (commit)
from 57ce53d8aac6dbd4ac10585b7b812c6021a19095 (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=a7bfb6c8dabcba6fb3534c4733d88fb9e466ae15
commit a7bfb6c8dabcba6fb3534c4733d88fb9e466ae15
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun Dec 3 10:54:02 2017 +0100
osmo-bts-octphy: Remove bogus warning about BS_AG_BLKS_RES
Contrary to osmo-bts-sysmo, the OCTPHY-2G does not have different L1
SAPI for AGCH and PCH. It uses cOCTVC1_GSM_SAPI_ENUM_PCH_AGCH for both,
and we convert that to the cbits=0x12 (Downlink CCCH) on the L1SAP.
The code above L1SAP can hence freely decide if it wants to respond with
an AGCH or PCH message, based on its knowledge of BS_AG_BLKS_RES,
without the OCTPHY specific code having to do anything about it.
Hence, there's nothing to do, and the warning can be removed
Change-Id: Ic1038b8dc57bdaf05493cd8479355b960275ea41
Related: OS#1575
-----------------------------------------------------------------------
Summary of changes:
src/osmo-bts-octphy/l1_if.c | 1 -
1 file changed, 1 deletion(-)
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)