I think the last device we sold was in 2011 and I am not aware
if anyone has used it for the last couple of years. Remove it
to lower the complexity of the builds.
* 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.
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.
Install the sysmobts firmware headers on top of the Osmocom toolchain.
This way the SDK can be used to re-compile both the OpenBSC and the
osmo-bts software.
Make sure the -dev package of the femtobts-api has not runtime
dependencies to a library that does not exist.
The name will be resolved to the hash during parse time. This will
not work when not having access to the internet. Use the sha1 sum
to make offline builds work.
Re-work the way we distribute the header and firmware files. The header
files may be accessed by everyone but the firmware may only be used by
owners of our device. Create a header only repository with all the header
versions of the firmware and create tarballs for specific releases that
will be provided to our customers. Use COMPATIBLE_MACHINE to pick the right
firmware and API version depending on sysmoBTSv1 and sysmoBTSv2.
Holger Hans Peter Freyther
Harald Welte
Holger Hans Peter Freyther
Holger Hans Peter Freyther