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/gerrit-log@lists.osmocom.org/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgPatch Set 1: > Ok, so why does this SAPI act failure does not manifest on regular > static channels? It DOES manifest in regular channels, as stated in the commit log. Maybe not clearly enough, but I'm all the time talking about a plain PDCH timeslot: it throws the error. Plain PDCH still works after that, because nothing else is done with it. The last PTCCH SAPI fails to be enabled, but no-one cares. A dyn TS sees the same behavior. The error is logged, but GPRS works. However, since the PTCCH SAPI act failed, further state of that TS is broken and dyn TS can no longer be used as TCH/*. So both plain PDCH and dyn TS see the same error and behavior, but for PDCH no further harm is done, while dyn TS stop working. That's why I fail to see how PTCCH UL activation can possibly solve any problem elsewhere: the SAPI is never enabled successfully. -- To view, visit https://gerrit.osmocom.org/671 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia59d95c75a8a5d3bd596f55cd1dc0906a6a95f7f Gerrit-PatchSet: 1 Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Max <msuraev at sysmocom.de> Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: neels_test_account <neels at hofmeyr.de> Gerrit-HasComments: No