Master has moved forward and we need to move the bbappends into the
yocto-edison folder. For the task-core-boot it has been renamed to
the packagegroup-core-boot and we do not need to increase the version
number for master.
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.
In the sysmoBTS 2050, we want to configure the 1PPS output of the
trimble to be active only if it has at least 1 satellite in view,
and want to make the receiver output its time information in UTC,
rather than GPS time.
sbts2050-util is a small binary-only userspace program used to
interface with the sysmoBTS 2050 board management controller,
i.e. to enable/disable PA power, read power consumption/temperature
and the like.
This tool is going to disappear once the respective features have been
included in the (open source) sysmobts-util / sysmobts-mgr. Please be
patient meanwhile.
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.
This is a osmo-bts that will use libosmo-abis for OML and RSL and
is based on master. In one way it should improve quality in another
it is also testing.
Additional applications might store files in /etc/default and it
is the easiest to backup up all of them. This has the danger that
after an upgrade the default file is not compatible/optimal but
we will need to deal with that once it occurs.
The sysmobts-v2 version was not installed because the file was
not called properly. Rename it to gpsd-default and the sysmobts-v2
version will be picked and installed.
GPSD 3.7 is somehow exiting without us really knowing the cause. The
version 3.9 has been released and we hope that it might just fix the
issues we are experiencing.
This is a bigger update and brings the SAPI queue, readv/writev
and realtime scheduling to the sysmobts software. This will greatly
improve the stability of the software under load.
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.
This way I just need to install sysmocom-openvpn-config and copy
a matching key to the device for the VPN config. The configuration
file is marked as a CONFFILE, this means that modifications to it
will not be lost during upgrade.
We have some images that need the real wget for upgrades, the SSL
root certificate of CA-Cert but that doesn't use task-sysmocom to
build the image. Move these utilities into the tools task.
The rootfs in the UBI is configured to grow to the full size of the
UBI, currently these are 999 LEBs (when there is no kernel volume)
but we had limited the LEBs the filesystem can hold to 400. After
this change the filesystem will grow from the 42MB to more than 120
MB.
I'm not sure if we really want to have a rootfs of that size but we
can at least experiment with it and see if the failure rate is changing
or not.
For the sysmoBTS we want to include a kernel volume inside the UBI as
a fallback in case the mounting of the main kernel is failing. We still
need to modify the boot command of the bootloader to look at this UBI
and to modify the kernel to include the tun/tap modules so the kernel
will be capable of opening a OpenVPN connection.
Currently one needs to write INHERIT += images_types_sysmo into the
conf/local.conf and add ubi-sysmo to the IMAGE_FSTYPES variable.
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.
This sanity check is included in the used bbclass directly and to
support both Edison and master we will need to remove the custom
python code due a change in indention in the python code.