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/power_control has been created
at f0bf5de82d48bca4e574469aa85a0e0ed146caae (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-bts/commit/?id=f0bf5de82d48bca4e574469aa85a0e0ed146caae
commit f0bf5de82d48bca4e574469aa85a0e0ed146caae
Author: Harald Welte <laforge at gnumonks.org>
Date: Sun Dec 13 17:08:13 2015 +0100
RSL: Be more spec compliant in terms of ms / bs power control
TS 08.58 requires that BTS-autonomous MS power control is _not_ used,
if only the MS Power IE is present in a channel activation. Rather, in
order to enable the BTS-autonomous power control loop, the MS Power
Parameters must be included.
So far we were always enabling MS power control, even in the absence of
the MS Power parmeters IE. This is fixed now. This meanas you will
need a correspondingly new OsmoBSC/OsmoNITB that sends this IE, or you
loose MS (uplink) power control altogether.
The content of the MS Power Parameters IE is parsed, but the threshold
values not used yet at this point.
-----------------------------------------------------------------------
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)