libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	lapd/test: Show dequeued messages	Jacob Erlbeck	2014-03-04	1	-4/+14
\| \| \| \| \| \|	This adds and uses a wrapper for lapdm_phsap_dequeue_prim() that prints information about the message that has been taken from the queue.
*	lapd/test: Add test case for RSL EST REQ -> LAPD	Jacob Erlbeck	2014-01-26	1	-0/+7
\| \| \| \| \| \| \| \| \|	This test case processes RSL establish requests for SMS (SAPI 3) on the SDCCH and the SACCH channels. The TX queues are checked after processing each message. Ticket: SYS#192 Sponsored-by: On-Waves ehf
*	lapd: The two known LAPDm issues have been addressed, update the test	Holger Hans Peter Freyther	2013-06-19	1	-2/+2
\| \| \| \| \| \| \| \| \|	The issue about the wrong padding has been found when creating the testcase in commit 15f740caa3a1ef681b3a5564daf6dfccb7b1e489 but the patch to fix that was never proposed by inclusion by its author. The issue about about the establish confirm carrying data with a wrong size is still present.
*	Fix: LAPDm contention resoltion must acknowledge subsequent SABM	Andreas Eversberg	2013-04-06	1	-0/+3
\| \| \| \| \| \| \| \| \|	After reception of SABM, the network responds with UA and enters the establised multiframe state. If UA is not received by mobile, the SABM is transmitted again, and the network must respond with UA again, unless it is from a different mobile. Add LAPDm collision test (contention resolution on network side).
*	lapd: Check in rslms_rx_rll() if lapdm context was initialized earlier	Daniel Willmann	2012-12-26	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This was found while implementing handover on a sysmobts. When we receive a channel release request for a channel that was never really activated (set_lapdm_context() was not called) we segfault in lapd_recv_dlsap(). We now return early with -EINVAL in rslms_rx_rll() if we receive a message that assumes set_lapdm_context() was already called. These are: * RSL_MT_UNIT_DATA_REQ * RSL_MT_DATA_REQ * RSL_MT_SUSP_REQ * RSL_MT_REL_REQ A test case was added to trigger the issue.
*	lapdm: Make sure that the msgb_l3len(msg) == length...	Holger Hans Peter Freyther	2012-01-12	1	-2/+2
\| \| \| \| \| \| \| \| \| \|	This code should not play with the internals of the msgb like this, this code got introduced in af48bed55607931307 and is breaking the osmo-bts usecase of forwarding an RSL message. Add a test case that fails without the new code. I would prefer if we could get rid of the manipulating the msgb like this, it is prone to errors like this one.
*	lapd_test: Look at the content of LAPD messages and compare them	Holger Hans Peter Freyther	2011-12-12	1	-0/+4
\| \| \| \|	Verify the output, accept two known errors in the generation of it.
*	lapdm: Create a simple test case to transmit data between both ends	Holger Hans Peter Freyther	2011-12-11	1	-0/+16
	This is testing the establishment of two ends (BTS, MS) one is in the polling mode as used by osmo-bts. Transfer data between the two ends. The sent data is not verified though. This should be followed up soon.