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/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/25201 ) Change subject: early IMM ASS: add configurable delay for RR IMM ASS ...................................................................... Patch Set 4: I understand why this patch exists, but I think it should not. I'd prefer to understand what exactly is creating a problem here, rather than introducing arbitrary configurable delays because we've seen those to work in one specific situation. If the channel is really active on the radio side [i.e.we are already transmitting valid downlink SACCH contents?], any IA after that point in time should not fail. Maybe there is a problem in osmo-bts-trx that makes it confirm channel activation too early towards the upper layers? Maybe this is "only" the rts-advance we're seeing here? I.e. channel activated in scheduler, but the PHY is still transmitting downlink bursts which were already pre-computed? In that case, shouldn't either the CHAN ACT ACK contain the exact frame number from which the channel will actually be active, or at least this newly introduced timeout correspond to the rts-advance / fn-advance? -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/25201 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: Ia1e63b98944dc840cde212fc732e20277cdc5585 Gerrit-Change-Number: 25201 Gerrit-PatchSet: 4 Gerrit-Owner: neels <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: Hoernchen <ewild at sysmocom.de> Gerrit-CC: fixeria <vyanitskiy at sysmocom.de> Gerrit-CC: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Tue, 17 Aug 2021 12:11:05 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210817/94851a3c/attachment.htm>