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

Age	Commit message (Collapse)	Author	Files	Lines
2019-01-17	trxcon/trxcon.c: do not expose tall_trx_ctx	Vadim Yanitskiy	1	-1/+1
	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/scheduler: separate logging of data messages	Vadim Yanitskiy	1	-1/+2
	Change-Id: I3a33687a688db2a183b546425f71c7a0a7030594
2017-11-19	host/trxcon/trx_if.c: separate logging of data messages	Vadim Yanitskiy	1	-1/+2
	Change-Id: I74ebe0441aeb41c324eafb6b586b2edd9ef4fd1a
2017-11-19	host/trxcon: separate logging of L1 Control and L1 Data	Vadim Yanitskiy	1	-1/+2
	L1 Data is quite verbose, while Control is typically limited. And if you would need to debug some Control message handling, the Data messages wont overflow your terminal anymore. This change introduces a new logging category named 'DL1D'. Change-Id: Id830c8bf913f7a8ddc87c47f70a337ee4623abd8
2017-11-19	host/trxcon/scheduler: add basic clock counter	Vadim Yanitskiy	1	-1/+2
	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 transceiver interface	Vadim Yanitskiy	1	-1/+2
	This is the second side of the 'OsmocomBB <-> SDR' bridge. Most of source code taken from the OsmoBTS project. Change-Id: I96fa3ada05d010f31af419a4950fd8ae2b62ef34
2017-11-19	host/trxcon: initial release of L1CTL interface	Vadim Yanitskiy	1	-2/+3
	There are two sides of the 'OsmocomBB <-> SDR' bridge. One of them is the L1CTL interface, which is used by existing layer23 applications to drive GSM L1. Exactly this interface is provided by the osmocon application, but instead of forwarding messages between both host software and firmware we need to handle incoming messages from layer23 applications, perform some GSM L1 specific conversations (coding, mapping, interleaving, etc.), then finally forward them to transceiver through the scheduler. And vice versa. This code is just a basic implementation of UNIX socket handlers, so currently we can only accept and drop connections from layer23 applications. Change-Id: I58d069bcc7742b42c0bf95e52063933bf2c352ff
2017-11-19	host/trxcon: introduce a new 'trxcon' application	Vadim Yanitskiy	1	-0/+11
	This app is similar to the osmocon, but designed to connect L2 & L3 apps with SDR transceiver insted of obsolete Calypso based hardware. Change-Id: Ie3c17f19aad9c26f3c49966a7c96b65911f62369