We have changed the strategy to support multiple BTS with a single
build but don't remove support from files that are used with Edison.
Linux 3.10 and systemd were not used with edison though. So we can
remove it. As the sysmobts-2050 extended the sysmobts-v2 build most
of the -sysmobts-2050 changes are not needed anyway.
This variable doesn't exist on dora and will not break things.
Fixes:
ERROR: Please ensure module rtfifo is listed in KERNEL_MODULE_PROBECONF since module_conf_rtfifo is set
The sysmobts-2050 machine does inherit from the generic bts so
we do not need an exact copy of the configuration file.
The watchdog is not used in dora or later images as this functionality
is integrated into the systemd.
Related: SYS#559
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.
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.
* to be able to mount vfat formatted
usbsticks we need the nls subsystem
* providing nls as modules is a bad idea because
you need to add them at image creation
* better include them into the kernel,
like the kernel for bts and bts-2050 does
We will change the MTD partitioning for our devices soon. The
kernel needs to honor the cmdline given by the kernel for that.
The rootfs will move a few pages to the back with newer bootloaders.
The name/structure of the NAT configuration was changed. Catch up
and put the new names into the old defconfig too. It is an ugly hack
to have it work with v3.2 and v3.10 kernels. The sysmobsc has been
fixed independently.
* use seperate defconfig, because of option changed from 2.6.39 to 3.10
* use python magic to switch between linux and linux-sysmocom
* add sysmocom-bsc to compatible machines for linux-sysmocom
* add new confiugration parameters for syslinux
This currently requires the meta-ti layer but we will make sure
that nothing from it will be required in the end. The kernel is
based on linux-3.2 as this is the "default" TI kernel that supports
the SGX (not that we care)
This is the latest stable kernel. I had hoped some crashes to
go away with it but it turns out to be a compiler issue that
we backported a patch for separately.
* The Linux 3.2.X kernel has some funny issues with GCC 4.8 in the
fs/namei.c look up code. It is easier to move to 3.10 than to fully
debug the issue.
* disable the mISDN loop patch for v3.10
* use the hack to make v3.2 compilable for edison and v3.10 for dora
this might help us in some installations where there are multiple
back-hauls and we want to base routing decisions not only based
on the destination IP.
The build differs in that it doesn't use a getty on ttyS0. In the fuutre,
a modified kernel serial driver as well as a 2050-specific utility
for managing the supervisor processor will follow.
The previous change modified the defconfig to not include the legacy
pseudo terminal support. Increase the version for the sysmoBTS to have
a kernel without old terminal files.
There is no need to have the various pty files clobber the /dev
directory when they are never used. Do not force a PR upgrade
right now as we don't have a good upgreade strategy for the v1
and the BSC config.
systemd is using the depedencies of the LSB section and according to
the debian documentation all applications accessing /var should depend
on the localfs. This makes the watchdog start properly on systemd systems.