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/.
Harald Welte gerrit-no-reply at lists.osmocom.orgPatch Set 2: > > Is the SW config contents not again "juts" some kind of TLV > structure? > > Unfortunately not. Neither Get Attribute Response Info nor > SW-Config are TLV-type structures. I've added clarifying comments > and references to the spec. I think those are too specific to > attempt to accommodate our TLV parser for such corner cases. But then why did we decide to use such an ugly mechanism to communicate parameters between BTS and BSC? I mean, we are not trying to be compatible with any existing code (as non exists for that) and just want to have a nice way how OsmoBTS communicates data with OsmoBSC, keeping the existing principles and the spirit of TS 12.21 OML. All the normal attributes of TS 12.21 managed objects are TLV encoded. The most straight-forward way from my point of view would thus be to use that structure? wouldn'y you agree? -- To view, visit https://gerrit.osmocom.org/2544 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I589be51daca0cb9e1f3473b93e910e46b06e23ae Gerrit-PatchSet: 2 Gerrit-Project: openbsc Gerrit-Branch: master Gerrit-Owner: Max <msuraev at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Max <msuraev at sysmocom.de> Gerrit-HasComments: No