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/OpenBSC@lists.osmocom.org/.
Holger Hans Peter Freyther holger at freyther.deOn Tue, Feb 18, 2014 at 12:34:26PM +0400, Ivan Kluchnikov wrote: > It seems, I don't understand what do you mean. > What access reference we should compare? > As I understand, each trx has one arfcn, so we can find trx by arfcn. bts 0 trx 0 arfcn 123 trx 1 arfcn 123 it is a config not rejected by OpenBSC. Maybe we should reject it, or we should make the deletion code more robust. I was referring to the request reference (10.5.2.30) of GSM 04.08. > > And besides that I would > > like you to move the look-up code to a separate function. That way we can > > at least write a unit test in the future. > > Ok, I can move this code to "gsm_bts_trx_by_arfcn" function. exactly