mirror of https://gerrit.osmocom.org/libosmocore
Pau Espin
c8772517d9
ARFCNs are values in well defined ranges. Until this patch, ARFCNs not belonging to any band were blindly assigned to DCS1800 by gsm_arfcn2band, causing unnoticed bugs and misconfigurations in osmo-bsc. Previous API gsm_arfcn2band cannot accomodate this kind of check easily, so let's deprecate it to tell people to use a new API gsm_arfcn2band_rc which performs this kind of checks and allows callers to log failures, misconfigurations, etc. At the same time, modify implementation of gsm_arfcn2band to abort if an invalid ARFCN is passed, this way users of this API can notice they are passing wrong data to it that most probably will produce unexpected results. Related: OS#3063 Change-Id: I780d452dcebce385469e32ef2fd844df6033393a |
||
---|---|---|
.. | ||
Makefile.am | ||
conv_codes_gsm.py | ||
conv_gen.py | ||
gen_website_doc_tree.sh | ||
osmo-arfcn.c | ||
osmo-auc-gen.c | ||
osmo-config-merge.c | ||
osmo-sim-test.c |