diff options
| author | Harald Welte <laforge@gnumonks.org> | 2012-05-31 23:15:38 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2012-06-01 00:06:58 +0200 |
| commit | 799ea59c2feeb9fe7ea9e9c202376e973ffca711 (patch) | |
| tree | 967a162fd8b11b2f078ef65fb27b1e696f0561b7 /contrib | |
| parent | 700c645478249319dcf7e7e138c13dbbb9c04ba9 (diff) | |
sysmobts: set the RF ACTIVE LED when we bring RF up
Once we get RF-ACTIVATE.conf from L1, we now enable the corresponding
LED. We also switch it off on RF-DEACTIVATE.conf. We do _not_ switch
it off when osmo-bts crashes or terminates before RF-DEACTIVATE.conf.
The latter is intentional, as RF may very well still be active at that
point. The re-spawning script will re-set the DSP and therby turn off
the RF and then disable the LED.
A better solution might be to do all this in the kernel driver for the
DSP.
Diffstat (limited to 'contrib')
| -rwxr-xr-x | contrib/respawn.sh | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/contrib/respawn.sh b/contrib/respawn.sh index d8c5d505..49ec3acd 100755 --- a/contrib/respawn.sh +++ b/contrib/respawn.sh @@ -1,5 +1,6 @@ #!/bin/sh while [ -e /etc/passwd ]; do cat /lib/firmware/sysmobts-v?.out > /dev/dspdl_dm644x_0 + echo "0" > /sys/class/leds/activity_led/brightness $* done |