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
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.
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.
* 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)