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.
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.
* Disable ext2/ext3 (as ext4 can be used to mount them).
* Enable AUFS/Squshfs support
* Misc improvements (e.g. ARM optimized AES code, disable
drivers/frameworks unlikely to be used)
Jan prefers to store the fully extended .config file so we will
do it. One advantage is to more easily see what has changed between
two kernel versions.
cp ../build.sysmobts/tmp/work/sysmobts_v2-poky-linux-gnueabi/linux-sysmocom/3.10.80+gitAUTOINC+3122273386-r43/git/.config ./recipes-bsp/linux/files/sysmobts-v2/defconfig
cp ../build.sysmobts/tmp/work/sysmocom_odu-poky-linux-gnueabi/linux-sysmocom/3.2.63+gitAUTOINC+3ed283bea6-r41/git/.config ./recipes-bsp/linux/files/sysmocom-odu/defconfig
cp ../build.sysmobts/tmp/work/sysmocom_bsc-poky-linux/linux-sysmocom/3.10.80+gitAUTOINC+3122273386-r43/git/.config ./recipes-bsp/linux/files/sysmocom-bsc/defconfig
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.
It seems like the kernel/package/upgrade/... proceess doesn't deal well
with the fact that some options used to be modules, which are now
built-in. Let's keep it as modules for the time being.
this enables conntrack events, ipset, ebtables, tc
scheduler/classifiers/ematches and much more.
it also disables the ATM code for which I don't think we have any use
case.
We want to use backported modules this means we need to make
some thing a module for it to work. Take Daniel's .config file,
run make savedefconfig and update our defconfig.
Related: SYS#850
We actually only use the PMIC (TPS65910) RTC in the hardware,
and not the AM335x RTC. Having a driver for a hardware that doesn't
receive actual backup voltage doesn't make sense.
We want to enable the watchdog in the bootloader already and
for this to be failsafe we need to have a kernel that can boot
and get ethernet without any additional modules. Now systemd
would not be able to trigger the watchdog and the system would
reboot within 60 seconds. I am not sure how the kernel upgrade
will go and we need to try this.
Related: SYS#374
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.
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)
* 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.
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.
Some of our target applications require ext3/ext4 support for mounting
an MMC card. While the sysmobts-v1 hardware does not have an external
MMC card slot it is nice to have the same image available for this
hardware.
The kernel has been rebased to target 3.2.40 with various bug
fixes in the upstream work. The sysmobts v2 config has been
changed to allocate space for two more UARTs. These are required
for the multi-trx configuration and they make a warning go away.
* Enable verbose detection, add CP2012 based serial adapter support
* Only enable USB1.1 HCD for now to fix the detection of the USB serial
adapters
* Enable more filesystems in the config to allow upgrading the boot
partition during the runtime (after installing the right codepage)
Pau Espin
Harald Welte
Holger Hans Peter Freyther
Jan Luebbe
Daniel Willmann
Henning Heinold
Holger Hans Peter Freyther
Holger Hans Peter Freyther