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.deHi Andreas, Harald, the recent "SI generation" fix broke multi trx setups. This is because when the first (c0) TRX is going up bts->si_valid will include SI2 and other SIs scheduled on the BCCH and once the second trx is going up the code decides it only needs to generate the SI5 (and more). But si_valid still includes SI2 and it will be set on the second trx. I have fixed it locally by setting si_valid to 0 early in the set_system_infos routine and added a warning for this case. How should this be properly fixed for master? Will the content of a specific SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the trx data structure? I have attached my local patch and would like to have a review for it. comments? ideas? holger