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

Age	Commit message (Collapse)	Author	Files	Lines
2012-11-20	Tell L1CTL_FBSB_REQ the expected received signal level	Harald Welte	1	-1/+2
	As Dieter points out, this drastically improves the resiliance to high receive levels on the C155. We cannot blindly assume a received signal level of -85 dBm if the BTS is 2m away and we actually receive -40 dBm. This patch extends the L1CTL_FBSB_REQ data structure in layer 1 with the respective field, as well as the l1ctl_tx_fbsb_req() API function called from the various layer23 apps. "mobile" and "bcch_scan" already did a PM request and thus know the expected signal power. "ccch_scan" and "cbch_sniff" apparently don't do, so the -85 dBm constant is now hardcoded into the host-side source code there, and should probably be fixed in a follow-up patch.
2011-11-13	host/layer23: Removed local copy of LAPDm, using libosmocore instad	Andreas Eversberg	1	-1/+0
	Since libosmocore already has LAPDm implementation, we don't need the local copy of LAPDm code anymore. Written-by: Andreas Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
2011-07-28	layer23: Add mobile support for sending / receiving voice frame through MNCC	Andreas.Eversberg	1	-2/+2
	Support GSM FR codec only so far. Written-by: Andreas Eversberg <jolly@eversberg.eu> Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
2011-06-24	fix some spillage from recent conversion	Harald Welte	1	-1/+1

2011-06-23	further decouple lapdm code from osmocom_ms and l1ctl	Harald Welte	1	-1/+1
	we introduce a new primitive layer betwen PH and DL, enabling the use of the LAPDm code in applications that are not based on L1CTL
2011-06-22	add l1ctl_proto.h #includes to lots of files	Harald Welte	1	-0/+2
	this is apparently a result of no longer including it indirectly via lapdm.h
2011-06-21	layer23: make LAPDm code mostly independent of 'struct osmocom_ms'	Harald Welte	1	-1/+2
	This is one step in the direction of re-using the lapdm code in osmo-bts.
2011-05-15	src: use namespace prefix osmo_* for utils	Pablo Neira Ayuso	1	-1/+1
	Summary of changes: s/bcd2char/osmo_bcd2char/g s/char2bcd/osmo_char2bcd/g s/hexparse/osmo_hexparse/g s/hexdump/osmo_hexdump/g s/hexdump_nospc/osmo_hexdump_nospc/g s/ubit_dump/osmo_ubit_dump/g s/static_assert/osmo_static_assert/g
2011-05-15	src: use namespace prefix osmo_signal*	Pablo Neira Ayuso	1	-1/+1
	Summary of changes: s/signal_cbfn/osmo_signal_cbfn/g s/register_signal_handler/osmo_signal_register_handler/g s/unregister_signal_handler/osmo_signal_unregister_handler/g s/dispatch_signal/osmo_signal_dispatch/g
2011-04-26	src: use new libosmogsm and include/osmocom/[gsm\|core] path to headers	Pablo Neira Ayuso	1	-5/+5
	This patch changes include paths to get osmocom-bb working with the current libosmocore tree. Among all these renames, you can notice several tweaks that I added on purpose, and that require some explanation, they are: * hexdump() in osmocon.c and osmoload.c has been renamed to avoid clashing with hexdump() defined in libosmocore. * gsmmap now depends on libosmogsm. Actually I had to cleanup Makefile.am because I was experiencing weird linking problems, probably due to a bug in the autotools. With the change included in this patch, I got it compiled and linked here correctly. This patch has been tested with the phone Motorola C123 and the following images files: * firmware/board/compal_e88/hello_world.compalram.bin * firmware/board/compal_e88/layer1.compalram.bin Using the osmocon, bcch_scan and mobile tools. Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org>
2010-12-27	layer23: Create an l23_app_info for various information and cb's	Holger Hans Peter Freyther	1	-0/+11
	Make it possible that each l23 app can inject the copyright string, also prepare to have callbacks for the config handling and other places. This will be useful to add app specific config options.
2010-11-21	host layer23: add a small cbch_sniff application	Alex Badea	1	-0/+188
	Tune to the ARFCN specified on the commandline (-a). Then, if a CBCH Channel Description IE is found in System Information Type 4, switch to dedicated mode on that particular channel to receive the CBCH.