This tuner is used for Xbox One Digital TV Tuner. It was added in kernel
4.16. I added clear comment, where it starts and where it ends to be sure
  that those comments can be removed as OpenWrt in their master branch
wants to have kernel 5.4, otherwise it should be there at least for
OpenWrt 19.07. Otherwise the kernel config won't be recognized.

This demodulator can be found, for example, in Astrometa DVB-T2 revision
2018. This enables it for kernel versions, but support for slave
demodulator was added in kernel 5.0.

Xbox One Digital Tuner is supported at mainline Linux since Kernel 4.16. OpenWrt
19.07 is using Kernel 4.14. This patch should not be send to OpenWrt for
branch master as they are working on 5.4 kernel support for targets.

Xbox One Digital Tuner uses:
- USB interface: dib0700
Patch 0032-generic-Add-support-for-Xbox-One-Tuner.patch,
which was backported adds USB ID 045e:02d5 to be recognized
for an USB interface dib0700.

- Demodulator MN88472, which is supported in kernel 4.14, which we are
  using and higher

- Tuner TDA18250B
Patch 0031-generic-add-tuner-driver-for-tda18250.patch,
which was backported add driver for this tuner.

This should be required to access whole memory.

This reverts commit 51b0ef62.

Netfilter sysctl defaults were moved into specific kmod-packages from
base-files. When we wanted it to configure in base-files, those values
are overwritten by file sysctl-nf-conntrack.conf provided in the package
kmod-nf-conntrack. We don't need to set it twice and remove it from
base-files and change it only in kmod-nf-conntrack.

Around a year ago this was lost in rebase. We need this to use whole
memory in Turris 1.x.

This drops activation for atsha services that do not exist any more
(they were replaced by preinit and uci-defaults).

Automatically enable zram.

Remove the part with PKG_RELEASE bump, so I dont need to rebase it
every time, when I bump syslog-ng in upstream

This fixes previous configuration rework. For some reason we lost DSA
(possibly in some rebase) and also devicetree was invalid. Compatible
field is primarily used to match drivers so changing it is no way
possible.

We provide now our own version of luajit package with moonjit. We can
later think about upstreaming it.

We can apply this patch to turris-os-packages directly now.

This patch was also incorect because of rebase. It talks about Kernel
4.19 but change happened in this development branch and was not taied to
Kernel 4.19 at all but rather applied to all versions.

This is new version of patch pulled from v4.1 branch of turris-build.

BTRFS in default is not compiled in and we use it as root-FS so it
should be.

This should be something we are going to upstream rather then this.

The device tree changed name.

This now uses default profile and is just one of boards in mpc85xx.

This should move Turris 1.x closer to upstream.

This removes all configuration options that were there to directly
influence kernel config instead of just OpenWrt one. This no longer
works so we can drop it.
Some of those options were moved to patches.
Other are active automatically because of OpenWrt default kernel
configuration and some were dropped without replacement.

This fixes target compilation for mvebu target as some patches are
adding additional options.

This is required because we no longer copy all CONFIG_KERNEL_ options to
platform kernel config file.

The host builds were intended for updater but we no longer build updater
trough OpenWrt build system so we no longer need these host builds.

Michal Hrusecky authored 5 years ago and Karel Koci committed 5 years ago

Need to fix dependencies because of upstream package split.

This fixes problem with preferences in feeds and removes patch required
to prevent such collision.

My patch, which was present in the hack folder, is no longer applying as
mariadb was updated in OpenWrt 18.06, 19.07 and master branches.
This patch was meant to be a workaround as something in OpenWrt was
changed and it caused inconsistency in the installation of packages and we
would like to have provided mariadb in our feed, this was the easiest
and a quicker solution at that time.

Solution is provided in this commit: a42ef21a740653ee76146bfccee1ab6afbd65539

The empty `space` variable in Makefile for hostapd was causing that
invalid Kconfig was generated and configuration phase failed.

This is happening only with latest GNUMake.