Having:
osmo-bts requires sysmobts-firmware > 3.11
sysmobts-firmware requires osmo-bts > 0.4.2
is something opkg can't resolve in one go. One needs two calls to
the opkg command to end up with a fully upgraded version. Make sure
that we require/pull newer firmware when installing a new version
of osmo-bts.
* Add sysmobts-firmware 3.11. The firmware will work with the
previous osmo-bts software and this one (as we don't use the
new primitives)
* Build newer version of osmo-bts with support for online
calibration and CMR fixes.
Enabling the "systemd" feature will enable the socket activation
feature used by systemd. This way we can (re-)start the GPSD based
on the socket activation.
If the year is smaller than < 2014 an initial date will be set. This
has been manually verified by copying ntpdate to ntpdate.off and making
sure that the VPN is coming up. Due the short SSL lifetime of CACert
we will need to update the script once in a while. But our VPN should
now always come up.
The TI Davinci DM644x and the TI Sierra AM335x both feature a
watchdog. Enable it on the AM335x as well. The next part is that
we can enable the watchdog for the shutdown. E.g. in case the
system does not reboot after the shutdown.
The shutdown is executed last and only after the shutdown target
has been reached. For time timeout we need to use the same interval
as the watchdog (as both drivers don't allow to change the timeout
interval).
Henning got really confused that the "a.b.c:1234" he passed to
gps2udp showed up as "a.b.c 1234" in the kernel cmdline. Use
strdup to take a copy of it.
Fixes: SYS#424
systemd doesn't look in /etc/rcS.d for init scripts so we never
start networking unless we are using ifplugd. We need to check
how this behves on the sysmobts and sysmobsc in case the network
is being started twice.
Build a version of barebox that has support for NAND flash and
ubifs. Load the kernel from the device. One needs to flash the
*mlo*.img into the xloader partitions and the other image into
the barebox partition.
erase /dev/nand0.xload.bb
erase /dev/nand0.xload_backup1.bb
erase /dev/nand0.xload_backup2.bb
erase /dev/nand0.xload_backup3.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup1.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup2.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup3.bb
This doesn't work like this. We need to know the _exact_ PV/PR
of the package and we don't. Specially with the PR server in dora
and later we can not know the version.
This reverts commit 767d7b6939.
So far we have used chrpath to fix the rpath we don't want but
this creates issues with supporting both dora and edison (we need
to depend on different recipes). Instead just force the RPATH to
be off. This can be done by setting the internal _RPATH variable.
I found this in Tool/gnulink.py.
This upgrades the firmware from 3.6 to 3.10. This is a significant
firmware upgrade and it changed ABIs too. Try hard to fix the
dependencies as much as possible. This requires the DSP headers
files to be of version 3.10 as well but we can not have versioned
DEPENDS.
The code has not been finished and doesn't meet the quality
standards we have for a product. Comment the sysmobts-mgr
related files that will be back soon.
We need to reduce the usage of ttyS0 to not conflict with the
sysmobts-mgr that opens and controls the power amplifier. This
is done by instructing systemd by config file to not log much
and disable the getty target.