We could add sanity checks for all newly deprecated collections and
distros here.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Followed up the project rename in the unified linux tree recipe.
Remaining change is the rename of the branch in the kernel repo and the
follow up change here.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Change variable name accross layers.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This commit still keeps the internal DISTRO variable name as-is and only
changes the longer free form version.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Fixes: https://git.ostc-eu.org/OSTC/planning/maintenance/-/issues/17


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

Fixes: https://git.ostc-eu.org/OSTC/planning/maintenance/-/issues/17


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

This fixes rauc-mark-good.service from failing before the first update.
Relevant upstream commits are:

 - https://git.ostc-eu.org/OSTC/OHOS/components/sysota/-/commit/b64ba55bda038170f70f8f537fc4768375aa80ad
 - https://git.ostc-eu.org/OSTC/OHOS/components/sysota/-/commit/13db00a25906e024b655fc7cdd02287aa852bc24
 - https://git.ostc-eu.org/OSTC/OHOS/components/sysota/-/commit/0eb9b2d24c744fd341b7ed77bed4b957548bd127

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/136


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

We don't want to build bind.

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

Using external dhclient brings ISC BIND libs into base image
Bind is heavy DNS server with big maintenance cost. We dont
want to ship neither bind nor bind-libs in the images.
Closes #151

Upstream-status: Not applicable

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

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

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

Having a runtime package management tool on a read-only filesystsem
doesn't help much. We could support something in that regards for
development mode but at this point we don't have a defined story for it.
So let's drop it to not confuse users.

Fixes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/148


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

The upstream qemu recipe uses host's pkg-config files as a solution to
detecting host's SDL[1]. This has a side effect of using other host
libraries that are later queried by the configure script. This can get
into a situation when the host provides libnfs (for example) and because
later this dependency is not in place anymore, qemu will fail at
runtime.

This change adds a PACKAGECONFIG definition for libnfs that is disabled
by default, in turn disabling by default pkgconfig autodetection in
configure.

[1] https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/qemu/qemu.inc?h=dunfell#n165

Fixes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/141
Upstream-status: Submitted [https://lists.openembedded.org/g/openembedded-core/message/156694

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

Hardcoding the root filesystem type to ext4 can't work as the default
rootfs type is squashfs. This patch fixes it by reusing the filesystem
type from ROOT_FSTYPE.

Fixes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/143


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

Andrei Gherzan authored 3 years ago and Pavel Zhukov committed 3 years ago

We already have NetworkManager which comes will all we need in terms of
DHCP support.

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

Fix bashisms to fix weston running under non-bash shells

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

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/139

Upstream-status: Submitted
Message-Id: <16AB6D14465C2628.4493@lists.openembedded.org>

ASOS images mount the platform boot partition at /run/mount/boot.
Adjust the Raspberry Pi 4 specific configuration file to express that
location.

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

Upstream-commit: b3a5b64f717b39536c96627ce058cf9c51cf3ba6
Upstream-status: Backport
Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/119

Eilís Ní Fhlannagáin authored 3 years ago and Eilís Ní Fhlannagáin committed 3 years ago

This is the first step in initiating automated package testing for
images. There will need to be some work on the CI side and some work on
the entire process but this is a first pass at getting the images to the
point where they have ptest on them.

This commit also adds an ext4 filesystem so we can test a writable
image. The wic image is still r/o but there is some benefit to having
tests run on a r/w fs.

Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>

Unless overridden in another layer or in local.conf, rauc will bundle
and use a know public key for verifying updates. This allows us to
to have some set of defaults that work out of the box and allow testing
the OTA stack and producing signed update bundles coming out of the CI
system.

The key is insecure and will expire in a year. This is intentional. Over
time we may switch to a reference key that is managed and secured or
re-generate another key for another year.

The insecure key has a fixed name and that name is used to trigger a
bitbake warning. OTA stack will learn to detect that key and similarly
warn users, or perform equally appropriate operations, in order to
reduce the risk of someone accidentally using this key in production.

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

The systoa package now provides standard sysotad.conf configuration
file, which is safe to install on all systems. For the MACHINE
"raspberrypi4-64" a special sysotad.conf is provided, one that
enables the pi-boot specific boot loader logic.

The entire sysota package becomes MACHINE-specific to avoid populating
the cache with the wrong config settings across builds.

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

The RAUC package contains the /etc/rauc/system.conf file, which defines
RAUC slot definitions and keyring file, which is used to verify updates.

The bbappend file makes the package machine-specific. For the MACHINE
"raspberrypi4-64" a canned system.conf is provided. For other machines
nothing, yet, happens.

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

By default, with no other configuration file, SystemOTA is inert and
safe to include in any system.

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

SystemOTA or sysota is a robust, unattended update system for Linux
Gateways, suitable for home automation gateways and other devices where
reliability is paramount.

This base recipe builds fine and works in Qemu. On a Raspberry Pi system
it needs to be paired with an appropriate RAUC configuration file and a
matching SystemOTA configuration file. Those will be provided with
specialized packages as the details are closely related to WIC images.

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

This issue is fixed upstream and we don't need to override the class
in downstream layers
This reverts commit 34449a8c.

Related: https://git.ostc-eu.org/OSTC/OHOS/manifest/-/issues/73


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

FreeRTOS switched to use main branch instead of master while our code
still looks for master. Overriding of bb class is needed for the change
thus it requires change in the order of layers.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/132


Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>
Upstream status: Backport
Upstream commit: d4bd9d748a4223856bf92dd35ca088d1f319d189

Eilís Ní Fhlannagáin authored 3 years ago and Eilís Ní Fhlannagáin committed 3 years ago

Looking at allscenarios-image-common.inc I see some devel/dbg packages
in there. These really should be pulled into a development or debug
image as images that endusers would build off of for a production
environment should only contain the minimal packages needed to run the system.

This patch removes gdbserver and packagegroup-net-tools (iperf3) from common
and puts them along with other useful EXTRA_IMAGE_FEATURES into two new images:

allscenarios-image-base-dev
allscenarios-image-extra-dev

Due to the size of the dbg-pkgs and dev-pkgs,
allscenarios-image-extra-dev needs a bump of it's ROOT_PARTITION_SIZE
else wic creation explodes.

Closes <issues 123>

Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>

The code detects when boot assets would overwrite something already
deployed/installed in the rootfs. This helps to avoid breaking packaging
at runtime. On the other hand, if IMAGE_BOOT_FILES has duplicates, this
check will fail when trying to install the same file multiple times. To
avoid this, treat the install_task as a set.

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

This implements logic as a rootfs postprocess command where the set of
boot artifacts are provided as part of the root filesystem. The reason
is that the system update components assume only the root filesystem as
part of the update payload while boot files are also needed depending on
the BSP. For example, RaspberryPi update process would update the kernel
and dtbs on the boot partition too.

The boot files are copied to the path defined by
ROOTFS_BOOT_ARTIFACTS_PATH, relative to the root of the root filesystem.

SOme of the logic in this mechanism are based on the current
implementation of the bootimg-partition wic plugin.

Fixes https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/104



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

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Bernhard Rosenkränzer authored 3 years ago and Pavel Zhukov committed 3 years ago

python3-pyelftools 0.26 can't handle DWARF-5, which is generated by default
by modern toolchains (clang 12+, gcc 11+).

Update it to 0.27 with an extra patch taken from upstream git to support
DWARF-5 so we can use it (e.g. in the Zephyr kernel test suite) without
switching the toolchains back to DWARF-4.

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

We first convert over qemuarm, qemuarm64, qemux86 and qemux86-64 to use
the common kernel.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

These will be similar to linux-yocto, but customized to the ASOS kernel
policies and support our reference HW.

qemuarm and qemuarm64 builds aren't yet supported by wic, but we can
still start building the kernels from a common base.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

This rename also better reflects the purpose of the file since it
reflects ASOS kernel policies.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

We have merged in the inclusion of NetworkManager in the reference
images so we can disable networkd to avoid runtime conflict.

Fixes https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/112



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

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

This provides a fully fledged network manager in our reference images.

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

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Bernhard Rosenkraenzer <bernhard.rosenkraenzer.ext@huawei.com> [adapted to current meta-ohos]