This removes duplicate kernelpackage for dvb-tuner-cxusb from DVB frontends
section. It is already present in DVB USB drivers section.

And removes two duplicate rows about dvb-tuner-dib0070.
Fixes:

tmp/.config-package.in:8717:	symbol PACKAGE_kmod-dvb-tuner-dib0070 is selected by PACKAGE_kmod-dvb-tuner-dib0070
tmp/.config-package.in:8717:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:8717:	symbol PACKAGE_kmod-dvb-tuner-dib0070 is selected by PACKAGE_kmod-dvb-tuner-dib0070

The support for it was added in Kernel 5.0. This backport it as it is.

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.

We have Storage plugin in Foris installed by default, but it is not
possible to use it without an installed NAS package list, which contains a
lot of packages. Let's move related support for USB Mass Storage devices
to kmod.list, which will be installed by default for all installations.

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.

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

This enables pseudorandom generator and dynamic variable "$RANDOM". It
will be quite useful and we wouldn't need to come with something crazy.

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

Automatically enable zram.

These packages can't be enabled for every single target. It is enough to
be marked as module to just compile them.

In reality we do not care about this configuration file and we plan to
drop it.

Setting -e in hashbang is not a good idea as users might just run it by
some other interpreter and that way removing (without noticing it) that
option.

This checks generated config after Kconfig pass if it still contains
preferences we have in files in configs directory.

This also drops some of the options in our config that are obsolete or
invalid.

CONFIG_VERSION_REPO is overwritten by setting pushed dynamically in
config by compile_pkgs so it makes no sense to have it here.

CONFIG_BUSYBOX_DEFAULT_CROND seems to be impossible to change and is
also default value that we later override with
CONFIG_BUSYBOX_CONFIG_CROND.

All PACKAGE options are not necessary. They are all enabled to 'm' but
getting them to 'y' would require a lot of works with gain that build
would in some cases failed instead of passed without that package. Not
worth it.

CONFIG_DEFAULT_TARGET_OPTIMIZATION is not applies so it is dropped here
without replacement. Same as one occurrence of CONFIG_CPU_TYPE.

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 problem that updater running is unable to handle alternatives
but with installing new one the script that was handling it previously
was removed. This installs one-time fix package that runs that original
script on its removal. The reason why on its removal is that it lets
first install all packages by original updater and new updater later
just removes this fix package and in that time it makes sense to
consitently update alternatives the same way as we did it previously
with postupdate hook script.

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.

Upstream fixed problem with invalid hash and that way broke validation
for some of the files. Updating to latest version of usign fixes this.

These packages are same as language packages for Foris

There is one speciality and that is that some of Luci's packages have
English localization package as well so we have to add "en" to
languages.

There is full list of all Luci applications there are in repository. We
should update this in future or modify the updater functionality so it
would be possible to check for existence of package in repository.

This has various advantages such as that we do not have to care to
always set appropriate requests for language packages as well as for
core package. It also ensures that localization is installed even if
package is installed outside of package list it is mentioned in.

There is also improvement for reForis. Now when you install reForis its
plugins are going to be managed relative to those requested to be
installed for Foris.

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

This was renamed in HBL to report.

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

This locks git mirror directory when we are updating mirrors. This
should solve race condition with multiple builds failing to update
mirrors and failing that way completely.

Only update is protected. The expectation is that initialization is
happenning only once and is protected by non-existence of directory. If
there is going to be problem with initialization as well then we can add
locking as well.

This is required for rainbow on Turris 1.x.

It is handy in general for any tool that needs to access memory mapped
devices or memory directly in general so it is enabled on all devices.