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/.
Max gerrit-no-reply at lists.osmocom.orgPatch Set 2: Well, yes and no. We have to pass several key-value pairs of arbitrary length. Each can be represented as TLV but all of them should be transferred as a collection of some sort. So we have to either write own one serializer/deserializer for such a collection or use existing one. I've opted for the latter and used sw-config which is also used in ipaccess firmware update so it has unit tests and a way to verify it against third-party implementation. Than there's question in which message to send it - I've got to either use existing attribute container as "Get Attribute Response Info" or put it into unspecified manufacturer-specific "Manufacturer Dependent Thresholds" for example. I've opted for former as at the time of writing I though I'd have to use other attributes in addition to sw-config so I'd have to somehow report unsupported attributes back. This have not materialized so I can rewrite it to use simpler manufacturer-specific container if you think it's better. -- 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