Hi.
This has been asked last year but to no avail, let's try again.
How logical channels are (de)activated in osmo-bts-trx? For example in all the other models there's sapi_deactivate_cb() callback but osmo-bts-trx doesn't seem to be using sapi_cmd at all.
To put this into perspective - while working on https://projects.osmocom.org/issues/1575 I got to activate/deactivate lchans when SI3 is received. This already works for sysmobts but I'd like to do the same for osmo-bts-trx as well.
Is there any documentation somewhere describing how it works there? Or maybe someone more familiar with the code could help to shed the light on it?
On Tue, Mar 14, 2017 at 06:41:20PM +0100, Max wrote:
How logical channels are (de)activated in osmo-bts-trx? For example in all the other models there's sapi_deactivate_cb() callback but osmo-bts-trx doesn't seem to be using sapi_cmd at all.
You could take a look at the dynamic timeslot implementation, i.e. bts_model_ts_disconnect() and bts_model_ts_connect(). The way it looks is that all you need to do is to set the new config of the channel. After all, osmo-bts-trx has no lower level hardware to be instructed to do anything, it's all in the structs in RAM: bts_model_ts_disconnect() for trx is empty. bts_model_ts_connect() basically just sets the new TS config using trx_set_ts_as_pchan(). I asked myself the same question back then, and in the end found out that simply setting the new config works fine.
I hope that helps ... and is even related to your question :)
~N
-
Max -
Neels Hofmeyr