osmo-bts - Osmocom BTS-Side code (Abis, scheduling)

Age	Commit message (Collapse)	Author	Files	Lines
2016-02-15	Introduce new phy_link and phy_instance abstraction	Harald Welte	1	-39/+94
	This way we can model a flexible mapping between any number of PHYs, each having multiple instances, and then map BTSs with TRXx on top of those PHYs.
2016-02-15	TRX: Move scheduler to src/common	Harald Welte	1	-1/+1
	This is the final step to make the L1 scheduler generally available to other BTS models than OsmoTRX.
2016-02-15	TRX: scheduler: Move trx_sched_clock() to scheduler_trx.c	Harald Welte	1	-2/+3
	This funciton (and associated static functions) are TRX specific, and scheduler.c should only contain generic code.
2016-02-15	TRX: scheduler: don't access l1h->config from scheduler	Harald Welte	1	-0/+4

2016-02-15	TRX: factor out the scheduler from remaining code	Harald Welte	1	-1/+1
	The L1 scheduler is a generally useful component that is unfortunately tied quite a bit into the OsmoTRX support. Let's try to separate it out by having separate per-trx/per-ts/per-chan data structures pre-fixed with l1sched_ Using this patch it should be one step easier to use the scheduler for other BTS models, such as the intended upcoming virtual BTS.
2016-01-16	TRX: replace some more 2715648 magic numbers with GSM_HYPERFRAME	Harald Welte	1	-3/+3

2015-09-22	trx: fix potential use of uninitialized toa variable.	Alexander Chemeris	1	-1/+1
	Not really a bug, as we're smart about it down the stream, but it's better to be strict here as well.
2015-09-22	trx: Send POWERON/OFF commands to osmo-bts only for the first channel.	Alexander Chemeris	1	-2/+8
	osmo-trx never supported separate power control for trx's, but now it started to be more strict about it.
2015-09-22	TRX: Check if Transceiver indicates an out of range clock	Andreas Eversberg	1	-7/+15
	If frame number is out of range (>= 2715648), the scheduler's process would end up in an infinite loop. This is because the loop would schedule bursts until the indicated frame number is reached, which would not be possible. The openbts, calypso-bts and osmo-trx might send out out of range clock indications every 3.5 hour.
2015-09-22	TRX: Show which TRX does not respond or rejects a command	Andreas Eversberg	1	-3/+4

2015-09-22	TRX: Handover access burst support	Andreas Eversberg	1	-0/+10

2015-09-22	TRX: Fixed typos tranceiver -> transceiver	Andreas Eversberg	1	-12/+12

2015-09-22	TRX: Fix: Cleanly free TRX instances during initialization in case of an error	Andreas Eversberg	1	-3/+3

2015-09-22	TRX: Add VTY options to enable and disable SETTSC and SETBSIC	Andreas Eversberg	1	-2/+12

2015-09-22	TRX: Implementation of MS power and timing advance loops	Andreas Eversberg	1	-1/+13

2015-09-22	TRX: Improved handling of clock indications.	Andreas Eversberg	1	-1/+4
	If no clock is received, a POWEROFF is sent until clock is detected.
2015-09-22	TRX: Fixes to TRX interface	Andreas Eversberg	1	-6/+7
	Ignore false response to uncritical commands.
2015-09-22	TRX: Minor fixes, especially handle TOA of RACH correctly	Andreas Eversberg	1	-3/+3

2015-09-22	TRX: Use received TRX clocks to determine availablility of tranceiver	Andreas Eversberg	1	-0/+6
	Only if transceiver becomes available, control commands are sent. If tranceiver is gone, reset scheduler. The current availability state is sent to BSC via OML state change commands.
2015-09-22	TRX: On negative response of critical commands, shutdown BTS	Andreas Eversberg	1	-23/+31

2015-09-22	TRX: Introduce osmobts-trx, a layer 1 implementation for OpenBTS tranceivers	Andreas Eversberg	1	-0/+495
	The code is quite complete, TCH and PDCH channels are not yet tested.