libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	lapd: Use LOGL_ERROR for messgaes that are wrong in the given context	Holger Hans Peter Freyther	2012-11-26	1	-14/+14
\| \| \| \|	Log message that are either too big or have the C/R bit set as error.
*	misc: Use static const struct for LAPD and Abis	Holger Hans Peter Freyther	2012-11-22	1	-1/+1
\|
*	lapd: Remove unused variable t200_start in lapd_acknowledge.	Holger Hans Peter Freyther	2012-03-16	1	-2/+1
\| \| \| \| \|	lapd_core.c: In function 'lapd_acknowledge': lapd_core.c:710:38: warning: variable 't200_start' set but not used [-Wunused-but-set-variable]
*	lapd: Warn if someone attempts to send an empty message	Holger Hans Peter Freyther	2012-01-12	1	-0/+7
\| \| \| \| \| \|	DATA REQ with a msgb_l3len(msg) == 0 message does not make any sense, log an error and return immediately before attempting to send an empty I frame in lapd_send_i.
*	lapd: Mention the L3 size of the payload being sent	Holger Hans Peter Freyther	2012-01-12	1	-1/+2
\|
*	libosmocore/lapd: Fixed handling of sequence errors at lapd_core.c	Andreas.Eversberg	2012-01-10	1	-3/+21
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	If a sequence error is received, the N(R) variable must still be used to acknowledge previously transmitted frames. If there are two subsequent sequence errors received, ignore it. (Ignore every second subsequent error.) This happens if our reply with the REJ is too slow, so the remote gets a T200 timeout and sends another frame with a sequence error. Test showed that replying with two subsequent REJ messages could the remote L2 process to abort. Replying too slow shouldn't happen, but may happen over serial link between BB and LAPD. Written-by: Andreas.Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	gsm/lapd_core: Make sure rc is initialize in lapd_rx_u	Sylvain Munaut	2011-11-20	1	-1/+1
\| \| \| \|	Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	lapd: Fixed possible double free buf in lapd_core.c	Andreas Eversberg	2011-11-12	1	-2/+3
\| \| \| \| \|	Written-by: Andreas Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
*	LAPD: Moved timer handling into seperate functions	Andreas Eversberg	2011-10-10	1	-72/+87
\|
*	Split of LAPDm into a core part and a GSM specific part	root	2011-10-10	1	-0/+2128
	Instead of mixing together the GSM layer 1 interface and RSL interface with the implementation of LAPD, the core function of LAPD is now extracted from LAPDm. The core implementation is now in lapd_core.c and lapd_core.h respectively. The lapd_core.c implements exactly one datalink instance for one SAP. The surrounding implementation "lapdm.c" codes/decodes the layer 2 headers and handles multiplexing and datalink instances, as well as translates primitives from/to RSL layer. lapd_core.c can now be used for other LAPD implementations. (ISDN/ABIS)