osmocom-bb - OsmocomBB MS-side GSM Protocol stack (L1, L2, L3) including firmware

Age	Commit message (Collapse)	Author	Files	Lines
2022-07-02	trxcon: group header files into 'include/osmocom/bb/trxcon'	Vadim Yanitskiy	1	-21/+0
	This is the first step towards the goal of moving the scheduler into a separate library. Change-Id: Ifa6137c239c215a3d323213ee74d34b419622be4 Related: OS#5599, OS#3761
2019-10-05	host/trxcon: add optional GSMTAP frame logging support	Vadim Yanitskiy	1	-0/+1
	This feature may be useful for our TTCN-3 testing infrastructure. By default it's disabled, and can be enabled using command line arguments of the main binary: ./trxcon -g 127.0.0.1 ... Change-Id: Iab4128fee5f18d816830fdca6c5ebebaf7451902
2019-01-17	trxcon/trxcon.c: do not expose tall_trx_ctx	Vadim Yanitskiy	1	-1/+0
	Both l1ctl_link_init() and trx_if_open() do accept 'tall_ctx' now, so there is no need to expose the root context anymore. For logging initialization, we can just pass a pointer. Change-Id: I7a2231eb880a995d3296b94481a7799e6ff07489
2017-11-19	host/trxcon: get rid of useless TRX_EVENT_RESET_IND	Vadim Yanitskiy	1	-1/+0
	Change-Id: I2aa4c000b37f64c351a806711b2d19bf27ef82bd
2017-11-19	host/trxcon: get rid of useless trxcon fsm events	Vadim Yanitskiy	1	-4/+0
	Both SCH_EVENT_CLCK_IND and SCH_EVENT_CLCK_LOSS were not handled, moreover there is no purpose to keep them. Change-Id: I8efac459a40f4287e3325890809991d5ef46e9b1
2017-11-19	host/trxcon: share trxcon fsm and talloc ctx via trxcon.h	Vadim Yanitskiy	1	-0/+3
	Change-Id: I9ef558f84a6dc1c9b8fc394c48e108676fa169f8
2017-11-19	host/trxcon: send L1CTL_DATA_IND directly from lchan handler	Vadim Yanitskiy	1	-1/+0
	Change-Id: Idfc86a59469c7a0bba1c16177502844e59ed8887
2017-11-19	host/trxcon: handle L1CTL_RESET_REQ inside l1ctl.c	Vadim Yanitskiy	1	-1/+0
	Change-Id: Ie5930dec800885784fb38ce6188c9c969cd2ad4e
2017-11-19	host/trxcon: handle L1CTL_FBSB_REQ inside l1ctl.c	Vadim Yanitskiy	1	-1/+0
	Change-Id: I5bcf39a20f1c6d3a2472e5e95725c6bb1c77bf5d
2017-11-19	host/trxcon/scheduler: implement xCCH decoding	Vadim Yanitskiy	1	-0/+1
	Change-Id: Ieb71e3727b525e85d161855973f63042366ccb05
2017-11-19	host/trxcon/scheduler: add basic clock counter	Vadim Yanitskiy	1	-0/+4
	The core of scheduler is a simple clock counter, which relays on system time for now. One was a bit simplified and migrated from OsmoBTS. Due to system time is not an ideal clock source, the counter should be periodically corrected by clock indications from BTS. Change-Id: I27d85bd3e2c8bca3f876f73517027b9fe43c9825
2017-11-19	host/trxcon: initial release of L1CTL handlers	Vadim Yanitskiy	1	-0/+2
	Now it's possible to handle the following requests from layer23 apps: - L1CTL_FBSB_REQ - L1CTL_PM_REQ - L1CTL_RESET_REQ - L1CTL_ECHO_REQ It should be noted, that the L1CTL_PM_REQ isn't handled correctly yet, due to required task isn't implemented on the TRX side yet. Instead of this, temporary we are sending some fake responses. Change-Id: I343eca3e20922ddd83e06231811200b26da442f3
2017-11-19	host/trxcon: integrate osmo-fsm framework	Vadim Yanitskiy	1	-0/+19
	This change introduces the following state machines: - trxcon_app_fsm - main application state machine. This state machine handles different events, raised from program modules (such as trx_if.c or l1ctl.c). - l1ctl_link_fsm - L1CTL server state machine. - trx_interface_fsm - TRX interface state machine. The program modules (such as trx_if.c or l1ctl.c) should be as much independent from each other as possible. In other words, one module should not call methods from another, e.g. L1CTL handlers are not able to send any command to transceiver directly. Instead of that, they should use shared event set to notify the main state machine about something. Depending on current state and received event, main state machine 'decides' what to do. This approach would allow to easily reuse the source code almost 'as is' anywhere outside the project. Change-Id: I7ee6fc891abe5f775f5b7ebbf093181a97950dea