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/.
Tom Tsou tom at tsou.ccHi Max, On Thu, Jun 8, 2017 at 1:49 AM, Max <msuraev at sysmocom.de> wrote: > The problem is that I don't understand how 2) will be handled by OsmoTRX? Shall I > expect 4 consecutive RACH messages via rx_rach_fn() in scheduler_trx.c in > osmo-bts-trx? Shall it be some other message/function? Will it be ignored/dropped > altogether by OsmoTRX? I'm not sure about osmo-bts-trx handling, but osmo-trx itself will unconditionally report any RACH bursts detected according to the active channel combination. Those are the only two conditions - that the channel combination indicates to perform RACH detection and that the RACH burst is detected. -TT