Since osmo-msc a2353c69cc3d2ccc7caee4571b3b8d2a98961150 and
osmo-bsc 3561bd48976dbee8dbd4659dad15be85a3e79ace osmo-bsc-mgcp support
is dropped in favour of osmo-mgw and one instance of osmo-mgw can be
shared between osmo-msc and osmo-bsc.
This patch is not longer used since the complete declaration of the
function was removed from the header file in osmo-bts
085569df55ceb3737b79f53b015b0c064698ddc6.
osmo-mgw recipe in meta-telephony has been updated to generate several
packages. Right now, osmo-bsc requires osmo-mgw service, but osmo-msc
still requires osmo-bsc-mgcp, so let's add both to the image.
After switch to linux 4.9.14, make oldconfig run by OE was disabling
CONFIG_IP_NF_TARGET_MASQUERADE even if original defconfig had it enabled
as a module. This target is required for osmo-ggsn.
This new package group contains what used to be the "task-sysmocom"
group, with an osmo-nitb. In turn, task-sysmocom.bb will be changed to
use new git repositories.
According to documentation, they are deprecated by
KERNEL_MODULE_AUTOLOAD:
WARNING: linux-sysmocom-4.9.14+gitAUTOINC+8d5d275254-r1 do_package: module_autoload_leds-gpio was replaced by KERNEL_MODULE_AUTOLOAD for cases where basename == module name, please drop it
After switch to linux 4.9.14, make oldconfig run by OE was disabling
CONFIG_IP_NF_TARGET_MASQUERADE even if original defconfig had it enabled
as a module. This target is required for osmo-ggsn.
WARNING: osmo-pcu-0.4+gitAUTOINC+0cd8e4eade-r5.18 do_configure: QA Issue: osmo-pcu: configure was passed unrecognised options: --enable-sysmocom-bts [unknown-configure-option]
Looking at ./configure --help in osmo-pcu, that option doesn't seem to
be available. The recipe is already using --enable-sysmocom-dsp too,
which is correct.
Commit d32cbbb13087eae2617920d4ea980f0e8869a89e changed --enable-sysmocom-bts to --enable-osmo-bts.
Later on, commit 08e5d604d3fce75b955549244b36fde62f20894b removed --enable-osmo-bts option.
In the past I copy and pasted the compiler-gcc4.h to have gcc-5.h and
gcc-6.h suffix. I didn't want to do the same for gcc7 and cherry picked
the original commit. Not compile tested though.
Current u-boot version cannot handle correctly ext4 formated with 64bit
option, which is enabled by default with recent versions of mkfs.ext4.
If option 64bit is enabled, u-boot reads the filesystem erroneously,
listing wrong directories or displaying some directories such as /boot
as empty, which forbids itself from loading the kernel and failing to
boot.
See #3733 and https://github.com/armbian/build/issues/279 for more
details.