openbsc - Legacy: OpenBSC, OsmoSGSN, OsmoBSC and other programs

Age	Commit message (Collapse)	Author	Files	Lines
2017-04-10	gsm_bts: add version and variant details	Max	1	-1/+1
	* add version string to gsm_bts * add PCU version string to gsm_bts * rename GSM_BTS_TYPE_OSMO_SYSMO -> GSM_BTS_OSMOBTS to avoid confusion between BTS model and variant * add variant enum to gsm_bts_model using enum with variants for each hw vendor of OsmoBTS * show connected PCU version (if available) in vty via 'show bts' This will come in handy when logging details regarding particular BTS reported via OML, see: Related: OS#1614 Change-Id: I6710d53115f34634a7b70969cc05fd5c72ff8ab2
2014-01-19	Do not expect all BTSs support TSC != BCC	Harald Welte	1	-0/+1
	We introduce a new feature indicating if the given BTS model supports a TSC that is different from the BCC (lower 3 bits of BSIC).
2013-04-29	sysmobts: Avoid a crash when trying to look-up a BTS	Holger Hans Peter Freyther	1	-17/+5
	The nanoBTS code is trying to find a struct gsm_bts based on the ipaccess_gsmnet and the ipaccess_unit data. The pointer is not initialized in the case of a sysmoBTS leading to a classic NULL pointer dereference. Move the feature init into the _init method. This way we can re-use the start code of the nanoBTS. This ensures that the ipaccess_gsmnet pointer is properly initialized and that the signal handlers are installed.
2012-07-02	BSC: introduce new "sysmobts" BTS model	Harald Welte	1	-0/+71
	so far, osmo-bts/sysmobts used to be entered as "sysmobts" type in the configuration file. However, there are some differences in the protocol/behaviour and we should reflect that by a new BTS plugin (with lots of code reuse from the nanobts driver).