Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

This reverts the following Debian packaging commits:

 - 82c843e: [arm64] Use armhf cross-compiler for building compat vDSO
 - 26d1417: [arm64] Fix dependencies on armhf cross-compiler
 - d067319: [arm64] linux-headers: Disable check for a 32-bit compiler

since armhf cross-compiler is currently not available on arm64.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Martyn Welch authored 5 years ago and Sjoerd Simons committed 5 years ago

Removing a USB device whilst it was throttled by the blkio cgroup
controller was found to result in a kernel panic. Add a backported set of
patches that fix this issue.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Enable pstore support for i.mx6 sabrelite boards. This helps debugging
hard crashes by saving console, panic and oops logs in reserved memory,
allowing to retrieve them after reboot.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

The apertis reference setup with a sabrelite has an LVDS screen but not
an LCD one; so disable the LCD one by default in the dtb

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

This configuration allows the kernel to boot on R-Car generation 3
boards again, after the merge in commit b2fccd75 regressed on
that front, losing the needed configuration entries.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Commit 8e1482b4 tried to bump the abiname to avoid incurring in
failures due to the module ABI in Apertis not matching the one in
Debian, but it had to be reverted as it introduced too much delta.

To address the ABI mismatch, simply disable the ABI checker, since
Apertis is not committing to a stable module ABI at the moment.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

This reverts commit 8e1482b4
"Bump abiname as we don't match the Debian kernel ABI" that was
introduced to avoid complaints from the ABI checker since the Apertis
kernel module ABI does not match the Debian one.

While most of the files got updated with the abiname bump, the
maintscripts have been left behind.

For this reason, the generated binaries are not shipping any
maintscript, causing all kind of breakage: for instance, the
`linux-image` packages misses the postinst script that trigger the
generation of the initrd, breaking the boot process.

Rather than introducing even more delta compared to the upstream
packaging, a later commit will simply disable the ABI check.

At the moment Apertis does not use the real-time kernels, so let's not waste
time on the builders.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Andrew Lee (李健秋) authored 5 years ago and Emanuele Aina committed 5 years ago

The ABI of the Apertis kernel packages does not match the one of the Debian
ones due to different configuration options.

In particular, disabling module signing changes the ABI signature of all the
symbols accepting a `struct module` parameter, for which we had a workaround in
https://gitlab.apertis.org/pkg/target/linux/commit/df5b937662ec9fb0

However on `armhf` we also disable Xen support (thus dropping all the
Xen-related exported symbols) and we enable modules that export symbols which
are not tracked by the Debian ABI reference, causing build failures.

We now simply recognize that the two Apertis and Debian ABI do not really match
(binary kernel module compatibility is not a goal at the moment) and thus we
bump the ABI name in `debian/config/defines`.

After that, generated files are updated with:

    $ fakeroot debian/rules debian/control-real

See more details at:
https://kernel-team.pages.debian.net/kernel-handbook/ch-versions.html#s-abi-maintenance



Signed-off-by: Andrew Lee (李健秋) <andrew.lee@collabora.co.uk>

Andrew Lee (李健秋) authored 5 years ago and Emanuele Aina committed 5 years ago

Signed-off-by: Andrew Lee (李健秋) <ajqlee@debian.org>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

When disabling module signing support, the `sig_ok` field of
`struct module` is dropped. This causes the CRC in `Modules.symvers`
for each symbol accepting a `struct module` to change, since
`genksyms` derives the CRC by recursively checking the definition
of each parameter.

This in turn means that when disabling modules signing support the
debian package build fails because the CRC checked by the ABI step
in `buildcheck.py` won't match the reference.

By making the inclusion of the `sig_ok` symbol unconditional the ABI
is now preserved.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Supporting cloud VMs is not a goal for Apertis at the moment, we lack
several other pieces for that and it just wastes build time.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Clean up a spurious change introduced during the last merge.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The `buildcheck.py` script now check the build kernels against a
reference list of symbols exported to modules to catch ABI breackages.

Unfortunately, it caused build failures since we don't export the
`fips_enabled` symbol. Its presence depends on the `CRYPTO_FIPS` config
option, which depends on the `MODULE_SIG` option: since we don't sign
our kernels (yet), the `CRYPTO_FIPS` option is automatically disabled
by Kconfig when `make oldconfig` is run during the build process.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Builds in the v2019 OBS were failing in the gencontrol target since the build
suffix used there is `v2019.0b1` and the regest was not matching the `.` dot.

This was not an issue in the `v2020dev0` project since its build suffix does
not contain dots:

    $ VERSION=4.19.37-5co1bv2020dev0b1; echo "$VERSION" | sed -rne 's,[^b]*b([a-z0-9]+)$$,\1,p'
    v2020dev0b1
    $ VERSION=4.19.37-5co1bv2019.0b1; echo "$VERSION" | sed -rne 's,[^b]*b([a-z0-9]+)$$,\1,p'
    4.19.37-5co1b1 # ARGH
    $ VERSION=4.19.37-5co1bv2019.0b1; echo "$VERSION" | sed -rne 's,[^b]*b([a-z0-9.]+)$$,\1,p'
    v2019.0b1
    $ VERSION=4.19.37-5co1bv2020dev0b1; echo "$VERSION" | sed -rne 's,[^b]*b([a-z0-9.]+)$$,\1,p'
    v2020dev0b1

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Commit infrastructure/apertis-docker-images@b9b045e8 "Use uncommon build
directory name" changed the build directory name from `build` to `_build`.

infrastructure/apertis-docker-images@b9b045e8



The change needs to be reflected here, as already done in
infrastructure/ci-package-builder@cbc8a0de.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Martyn Welch authored 5 years ago and Andrej Shadura committed 5 years ago

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 5 years ago and Andrej Shadura committed 5 years ago

A bug has been found in Apparmor, resulting in dbus policies which aim to
deny specific dbus transactions failing to work. The latest series of
patches made available as part of the Ubuntu Apparmor support
(specifically "UBUNTU SAUCE: apparmor: fix apparmor mediating locking
non-fs, unix sockets") was found to resolve this bug.

Add the additional available Apparmor patches, available as part of the
"5.1-outoftree" branch at https://gitlab.com/apparmor/apparmor-kernel

.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

This patch adds support for running the Apertis 4.19 kernel on the
Raspberry Pi CM3 module plugged on top of the MyPi Industrial IoT
Integrator I/O Board

APERTIS-6053

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Enable Xen forces CONFIG_ARCH_DMA_ADDR_T_64BIT=y even on 32 bit arm;
Which unfortunately exposes bugs in the CAAM driver. Disable it for now
as we don't care about it for Apertis.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Enable the onboard crypto engine found in various freescale devices.
Build as builtin as the module doesn't auto-load.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>