libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	coding: Add BER-reporting RACH decode functions	Harald Welte	2018-02-26	1	-2/+8
\| \| \| \| \| \| \| \| \| \| \| \|	For all other decode operations we report the BER, but not for the RACH. This results in osmo-bts-trx not being able to report BER to the higher layers, which is possible on other BTS backends. Let's close this gap by introducing gsm0503_rach_ext_decode_ber() and gsm0503_rach_decode_ber() with the usual n_errors / n_bits_total arguments. Change-Id: I2b1926a37bde860dcfeb0d613eb55a71271928c5
*	Add functions for extended RACH coding	Max	2017-12-11	1	-1/+6
\| \| \| \| \| \| \| \| \| \| \|	Add support for extended RACH (11 bit) according 3GPP TS 45.003 §5.3.2: * convolutional code with puncturing * encoding/decoding routines * corresponding tests Change-Id: I85a34a82d5cd39a594ee89d91a2338226066ab5d Related: OS#1548
*	doxygen: unify use of \file across the board	Neels Hofmeyr	2017-06-23	5	-25/+25
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Considering the various styles and implications found in the sources, edit scores of files to follow the same API doc guidelines around the doxygen grouping and the \file tag. Many files now show a short description in the generated API doc that was so far only available as C comment. The guidelines and reasoning behind it is documented at https://osmocom.org/projects/cellular-infrastructure/wiki/Guidelines_for_API_documentation In some instances, remove file comments and add to the corresponding group instead, to be shared among several files (e.g. bitvec). Change-Id: Ifa70e77e90462b5eb2b0457c70fd25275910c72b
*	doxygen: enable AUTOBRIEF, drop \brief	Neels Hofmeyr	2017-06-23	5	-5/+5
\| \| \| \| \| \| \| \| \| \|	Especially for short descriptions, it is annoying to have to type \brief for every single API doc. Drop all \brief and enable the AUTOBRIEF feature of doxygen, which always takes the first sentence of an API doc as the brief description. Change-Id: I11a8a821b065a128108641a2a63fb5a2b1916e87
*	Move NUM_BYTES macro to core library	Max	2017-06-19	1	-1/+0
\| \| \| \| \| \| \| \| \|	It's universally useful so it make sense to have it in the shared core: * move macro from libosmocoding to libosmocore * add OSMO_ prefix * add doxygen docs Change-Id: I5386ba3e1f1cc153ba96c29dc71c9075a052aa02
*	gsm0503_interleaving: Mark input arguments as 'const *'	Harald Welte	2017-06-12	1	-5/+5
\| \| \| \| \| \| \|	The interleaving/deinterleaving functions were missing 'const' qualifiers on their input data buffers Change-Id: I2118c34a6353167787b23f877f1d81d60151aaf9
*	Add doxygen documentation to libosmocoding	Harald Welte	2017-06-12	5	-0/+50
\| \| \| \| \| \| \|	This adds the minimum amount of API documentation that we should have on all our code, particularly new code merged into a library. Change-Id: I526804f64313867913574e50e5b9e9205ad3aa74
*	gsm0503_{coding,mapping}: Mark input arguments as 'const'	Harald Welte	2017-06-12	2	-21/+21
\| \| \| \| \| \| \| \|	It is generally our coding style to mark pointers to constant input data as 'const *'. For some reason the gsm0503 coding and mapping was not adhering to this, so let's bring it into compliance. Change-Id: Id8731d7ae6171dff94741b6ddbb95ab5f03bfd4e
*	libosmocoding: migrate transcoding routines from OsmoBTS	Vadim Yanitskiy	2017-03-07	5	-0/+210
	There are some projects, such as GR-GSM and OsmocomBB, which would benefit from using one shared implementation of GSM 05.03 code. So, this commit introduces a new sub-library called libosmocoding, which (for now) provides GSM, GPRS and EDGE transcoding routines, migrated from OsmoBTS. The original GSM 05.03 code from OsmoBTS was relicensed under GPLv2-or-later with permission of copyright holders (Andreas Eversberg, Alexander Chemeris and Tom Tsou). The following data types are currently supported: - xCCH - PDTCH (CS 1-4 and MCS 1-9) - TCH/FR - TCH/HR - TCH/AFS - RCH/AHS - RACH - SCH Change-Id: I0c3256b87686d878e4e716d12393cad5924fdfa1