libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	doxygen: unify use of \file across the board	Neels Hofmeyr	2017-06-23	1	-7/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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	1	-28/+28
\| \| \| \| \| \| \| \| \| \|	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
*	include: Switch to #pragma once pattern	Sylvain Munaut	2014-06-16	1	-4/+1
\| \| \| \|	Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	misc: Doxygen tweaks: fixed some typos and minor errors	Katerina Barone-Adesi	2013-02-15	1	-1/+1
\| \| \| \| \|	Doxygen generates quite a lot of warnings on libosmocore. Some of them are obvious typos - this patch aims to fix such low-hanging fruit.
*	doc: Fix the Doxygen section endings	Sylvain Munaut	2012-04-18	1	-1/+1
\| \| \| \|	Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	core/conv: Add utility methods to know length of coded/decoded vectors	Sylvain Munaut	2011-11-24	1	-0/+6
\| \| \| \|	Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	core/conv: Add support for other termination types (trunc & tail biting)	Sylvain Munaut	2011-11-24	1	-6/+25
\| \| \| \| \| \| \| \|	Note that this breaks the ABI and the low level API. But it shouldn't break the high level API, nor the conv code definitions (because fields default to 0, and for new fields '0' is the previous behavior) Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	core/conv: Minor documentation improvements	Sylvain Munaut	2011-11-24	1	-12/+18
\| \| \| \|	Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	some more doxygen work (include the notion of modules)	Harald Welte	2011-08-17	1	-11/+25
\|
*	core/conv: Add some generic code for convolutional coding/decoding	Sylvain Munaut	2011-04-26	1	-0/+101
	Far from perfect but suits our need thus far. The viterbi with softbit input is quite cpu-intensive. Since most received bursts are often mostly error free, you could use a less cpu intensive algorithm (Fano ?) and with hard bit input. Then only switch to viterbi soft bit input if the channel is bad enough to justify it. Soft output is not implemented as its usefulness for the block coding is limited. Signed-off-by: Sylvain Munaut <tnt@246tNt.com>