- Mar 24, 2022
-
-
As defined on https://booting.oniroproject.org/distro/infra/ Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
-
Historically the DCO check was routed to a dedicated but slow machine that guaranteed that no CI would be stuck waiting on the miniscule compliance job. With the Eclipse migration and CI/CD being slightly out of our control, it's just more convenient to drop this tag rather than request configuration change in the instance. Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
-
Historically the REUSE check was routed to a dedicated but slow machine that guaranteed that no CI would be stuck waiting on the miniscule compliance job. With the Eclipse migration and CI/CD being slightly out of our control, it's just more convenient to drop this tag rather than request configuration change in the instance. Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
-
Andrei Gherzan authored
This is now the currently main development branch. Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
The repository holding the repo manifests is now under Eclipse infrastructure. Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Pavel Zhukov authored
Template has been taken from old gitlab instance. Signed-off-by:
Pavel Zhukov <pavel.zhukov@huawei.com> (cherry picked from commit d79daf1c)
-
- Mar 22, 2022
-
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Make sure we explicitly set up the WKS file for both C61 targets after the target rename. Signed-off-by:
Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Update the names used for C61 targets, there are now two instead of one before. Signed-off-by:
Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
C61 build has been split up from the target MACHINE=seco-imx8mm-c61 to two targets, MACHINE=seco-imx8mm-c61-2gb and MACHINE=seco-imx8mm-c61-4gb, depending on the memory on the card. Reflect that in the build instructions. Signed-off-by:
Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
- Mar 21, 2022
-
-
Davide Gardenal authored
Move compiler security options from only linux to all kernels Signed-off-by:
Davide Gardenal <davide.gardenal@huawei.com>
-
Esben Haabendal authored
It is obviously convenient to be able to provide an SDK with GN support, for a one-stop solution to offering projects such as OpenHarmony with a replacement toolchain. Signed-off-by:
Esben Haabendal <esben.haabendal@huawei.com>
-
- Mar 18, 2022
-
-
Bernhard Rosenkränzer authored
Fix go hardcoding glibc's dynamic linker location into musl binaries Signed-off-by:
Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>
-
- Mar 17, 2022
-
-
Stefan Schmidt authored
The Raspberry Pi upstream kernel tree has been rebased and the git revision referenced to fetch has disappeared. After the update in meta-raspberrypi to a working revision we can now bump and fix fetch problems in Oniro. Signed-off-by:
Stefan Schmidt <stefan.schmidt@huawei.com>
-
- Mar 14, 2022
-
-
Stefan Schmidt authored
With OpenHarmony and Matter we have two projects using GN as their build system. To support the gn.bbclass we have in Oniro we need a gn-native recipe as well to support building these projects. While progress is being made to upstream gn-native to meta-oe we keep a copy here to have a working build. The alternative would be to add two extra layers to our build for just one recipe. This file need to be removed once upstreamed into meta-oe. The original source of this file is here: https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-devtools/gn/gn_git.bb Signed-off-by:
Stefan Schmidt <stefan.schmidt@huawei.com>
-
Recipe for the Matter networking protocol (formerly known as CHIP). This project has more the form of a vendor SDK with support for many bare metal SDK's as well as various operating systems. This recipe does focus on the Linux build and configures the project to disable all extra third_party git submodules (we only use 6 out of 48). Matter uses the GN meta build system, therefore using gn.bbclass as a base for the recipe. gn.bbclass requires patching BUILDCONFIG.gn file to set default toolchain and add compiler/linker flags to the yocto-provided ones. Mbedtls version integrated in Matter doesn't compile cleanly with GCC v11. It is not required by currently used Linux target but in case it's needed version provided by the Yocto build system shall be used instead of this integrated one and therefore disabling building of the mbedtls completely. Signed-off-by:
Robert Drab <robert.drab@huawei.com> Signed-off-by:
Stefan Schmidt <stefan.schmidt@huawei.com>
-
Andrei Gherzan authored
This bump fixes the layer with the new restructuring of the override system in meta-freescale. Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
sysota is a go project using go modules. Due to how this support is currently implemented in the core, the recipe will download the dependent go packages during compile. On the other hand, lately, the core also defaulted to a restricted network environment in the compile task breaking (but for good reasons) the compilation of sysota. This situation was done as a forcing function for the community to react and improve the current implementation of go mods in the core. For now, we workaround it as this doesn't change the current limitations/behaviour while we investigate better options in the core. Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
oe-core completely dropped the associated class and support: https://lists.openembedded.org/g/openembedded-core/message/160848 This change drops the associated references in our build sample files. Signed-off-by:
Andrei Gherzan <andrei.gherzan@huawei.com>
-
Andrei Gherzan authored
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>
-
- Mar 08, 2022
-
-
Zygmunt Krynicki authored
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>
-
- Feb 25, 2022
-
-
Zygmunt Krynicki authored
The COMPATIBLE strings are set to "QEMU x86" and "QEMU x86-64" respectively. The values are not standardized, but since the idea is that bundles with a matching COMPATIBLE string can be used for updates, picking a generic value is most appropriate. Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
-
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
Chase Qi authored
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
- Feb 24, 2022
-
-
Chase Qi authored
This helps to understand that the actual interpolation process cannot use syntax like bash/sh. In addition, putting the @ sigil at both ends so that @FOO_BAR is not incorrectly replaced as well. Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
Chase Qi authored
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
Chase Qi authored
Set lava-test and lava-report job as scheduled pipeline only for the below reasons. * lava-test requires token set using GitLab variable for job submission * lava-report depends on all test jobs Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
Chase Qi authored
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-
- Feb 22, 2022
-
-
Zygmunt Krynicki authored
The x-gpt-efi-disk kickstart file has a duplicate --boot argument for the boot partition. One uses the BOOT_PARTITION_LABEL variable. The other uses a hard-coded string "boot". Drop the hard-coded value. Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
-
Chase Qi authored
Signed-off-by:
Chase Qi <chase.qi@linaro.org>
-