Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Luca Seritan <luca.seritan@huawei.com>

This machine is based on Cortex-A57. For the EFI side, it uses
edk2-firmware.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Luca Seritan <luca.seritan@huawei.com>

This machine is based on Cortex-A15 with softfp (to avoid hacks on grub
side as it requires softfp or a way to force flag to softfp). For the
EFI side, it uses edk2-firmware.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Luca Seritan <luca.seritan@huawei.com>

BB_DANGLINGAPPENDS_WARNONLY controls how the parser behaves when
dangling bbappends are found. When not defined (or defined to 0/no), it
errors out and forces for these to be updated and handled accordingly.
We rely on this behaviour to force us to forward port changes or drop if
needed. The problem is that some layers might (in various ways) define
this to only warn in this case breaking our CI and project health
assumptions.

To avoid this, we force this in the inc included by all our distros.
Doing this in local.conf is problematic this would change behaviour by
just importing a layer.

Fixes: #751



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Order is important here as we might want to override things that are
defined strictly in the freertos.conf distro.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The most important elements of this include file is the OpenHarmony
version definition along with the associated preferred version.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This is required on recipes like
oniro-openharmony-toolchain-integration provided by meta-openharmony.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This avoids build warnings and it is in line with what meta-openharmony
is using.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Re-allow overriding of TCLIBC via local.conf/shell env.
Upstream part has been merged into kirkstone branch:
oe-core:e30ef926e440b505e93e404c056034d86364a241

Fixes: #608

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

This fixes oniro-image-[base, extra]-dev do_image_wic task.

Signed-off-by: Davide Gardenal <davide.gardenal@huawei.com>

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

wheel group doesn't exist in oe-core/oniro but systemd is build with
wheel group support. This causes ACL warnings during boot process.

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Without bootindex option qemu doesn't respect boot order when
booting with EFI and writes wrong boot order information into the ovmf
image which breaks boot order permanently.

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Right now, we do a remove in DISTRO_FEATURES, that, while we don't
neccessarily support them, due to the finality of :remove we force our
end users to not use them either.

By moving DISTRO_FEATURES:remove to DEFAULT_DISTRO_FEATURES:remove, we
allow end users to still use oniro.conf but add in those removed
features.

We also move IMAGE_FEATURES from a distro level var to the image.
IMAGE_FEATURES should generally be put in image recipes. This also gives
end users a way to use Oniro and work around our :remove defaults.

Signed-off-by: Eilís Ní Fhlannagáin <pidge@pidge.org>

Zygmunt Krynicki authored 3 years ago and Andrei Gherzan committed 3 years ago

This saves half of the space used by compressed disk artifacts.

I ran into the issue when creating grubenv recovery logic. To my surprise
the execution flow ended up in the case where both slots are available
and timestamp on the kernel is used to break the tie.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Move compiler security options from only linux to all kernels

Signed-off-by: Davide Gardenal <davide.gardenal@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Upstream moved the default definition of TCLIBC as part of:

commit 57aa60ef6422568b425b6ccc4451567efc578469
Author: Martin Jansa <Martin.Jansa@gmail.com>
Date:   Wed Sep 16 15:28:52 2020 +0200
    bitbake.conf: use ${TCMODE}-${TCLIBC} directory for CACHE

This moved TCLIBC from defaultsetup.conf to bitbake.conf but the problem
is that it did it before the place were bitbake.conf includes the distro
configuration changing its behaviour. With this change, a ?= in the
distro configuration will be ignored as the first one is already
defined in bitbake.conf.

Because of the above, we ended up with defaulting to glibc. We revert
this by forcing the value of TCLIBC accordingly. This will have a side
effect that shell environment variable will be ignored. So doing that
through BB_ENV_EXTRAWHITE will be broken from now on. If we want that
ability in the future, we can try to address.

Fixes: https://booting.oniroproject.org/distro/oniro/-/issues/252



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The oniro-grub-bootconf recipe provides the virtual-grub-bootconf
package which in turn contains a stub grub.cfg and empty grubenv file.

The change is spread around a considerable number of areas. Specifically
the kick-start file needs to explicitly reference the grub.cfg file which
must be placed in the wic/ directory. Since we need the same file in
grub/files directory, so that it can be installed into the image,
a symbolic link is employed.

The distribution configuration file, oniro-linux.conf sets
IMAGE_EFI_BOOT_FILES so that the grubenv file is installed into the boot
partition. This is required since grub cannot create the file by itself,
it can only edit the file, in-place, if it is present there already.

The actual configuration file for GRUB is a stub. Appropriate file with
some non-trivial logic will be proposed separately. The stub file boots
the first slot all the time. The kernel is loaded from the rootfs.

This test-boots fine in x86 and x86-64 qemu builds.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Similar to how the SECO board was handled, the QEMU x86 machine can now
use EFI and GRUB correctly. This change is split over three parts,
MACHINE_FEATURES is modified to enable efi, WKS_FILE_DEPENDS to build
EFI firmware and lastly WKS_FILE to pick the new unified kick-start
file.

This was tested with:

        qemu-system-i386 -cpu IvyBridge -machine q35 -bios ovmf.qcow2 \
                oniro-image-base-qemux86.wic -m 1024 -nographic

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Similar to how the SECO board was handled, the QEMU x86-64 machine can
now use EFI and GRUB correctly. This change is split over three parts,
MACHINE_FEATURES is modified to enable efi, WKS_FILE_DEPENDS to build
EFI firmware and lastly WKS_FILE to pick the new unified kick-start
file.

This was tested with:

        qemu-system-x86_64 -cpu IvyBridge -machine q35 -bios ovmf.qcow2 \
                oniro-image-base-qemux86-64.wic -m 1024 -nographic

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Prefer GRUB as the EFI provider.

The SysOTA+RAUC stack supports GRUB as the point of integration. This is
caused by both RAUC downstream support for GRUB and GRUB's ability to
load the kernel from a squashfs image.

In addition, add TODO about GRUB and microcode updates

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

One too many O's.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

With the master/kirkstone update, the rootfs grew by around 0.5G.
Accomodate this growth for now in the wic configuration.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Oniro is based on wayland for the graphics stack. There is no testing
nor support for x11 so let's drop it in the distro's default
configuration.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

All these were needed for backporting 5.10 on dunfell. Now that the
meta-raspberrypi was updated, we have all we need in the BSP layer.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The reproducible_build bbclass was merged in base hence enabled by
default now.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

These are now aligned with oe-core defaults so no need for any
additional configuration here.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This was a relic from poky distro but there is no need to pull in
packagegroup-core-device-devel by default. In the meanwhile poky distro
also dropped it.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

meta-security and meta-rauc are now enabled via a distro feature:
security and rauc respectively.

Also, pam is a required distro feature for packagegroup-core-weston.
This due to weston-init requiring pam if started via systemd.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Major changes have been included with the kirkstone/honister update so
let's bump LOCALCONF_VERSION for compatibility.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The codename should be the oniro codename of a specific release. For the
development branches, let's use something generic like 'dev'.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

In the preparation of kirkstone update, we add compatibility for
honister until upstream releases the new LTS version.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>