Merge in ICO/coreos from add_variable_for_kernel_in_wks_file to master
* commit 'afa1a784c1637ad2965f93061794f10577e992a2':
refactor(partitions.inc): use variable for kernel in wks file
the changed image is
layers/meta-belden-coreos-demo/recipes-core/image/cores-image-demo-k3s
k3s is a orchestration tool and a slimed down version of kubernetes
k3s agent is a tool to control pods
the commands come a k3s server in a cluster
Now the distro settings is splitted into two config smaller config
file. PACKAGECONFIG for the system package is set to include a
reduced set of features by default.
Some EFI related feature are now dependant of the EFI DISTRO_
and MACHINE_FEATURES.
Now a single unified kernel image is built using a new CoreOS
specific functionality added in the efibootguard UKI stub to
automatically insert root=PARTLABEL=rootfs0 (or rootfs1) in the
kernel command line
BREAKING CHANGE: coreos-image-uki.bbclass now only generate a
single kernel image named kernel-${MACHINE}.efi
Merge in ICO/coreos from fix_pci_issue_on_cf_pro_eval_board to master
* commit '1d8551459f909b00e0156959a40ac3cbc9773ef5':
fix(u-boot): revert to u-boot 2019.10 because of several issues with 2023.04
Merge in ICO/coreos from feat/extlayers to master
* commit '0d5beff86fd830f8b3eec81afdf51f94132530b6':
feat(layers): move third party layers to external-layers
* the swupdate version has been updated and therefore caused a regression
because the bbappend didn't match anymore.
* changed the bbappend to match any swupdate version.
BREAKING CHANGE: bblayers.conf / bblayers.conf.sample of project
using CoreOS should be adapted to use external-layers instead
of layers for each moved layers
Reason was that the actual firmware was just added to the coreos-image-all-feature.
* use MACHINE_ESSENTIALS_EXTRA_RDEPENDS instead of IMAGE_INSTALL and move to machine config
* refined linux-firmware recipe to just have microchip on its own.
Merge in ICO/coreos from fix_falcon_phy_firmware to master
* commit 'e003ccb91319299b73eaf8029288e3fde55fc71f':
fix(cn9131-bldn-mbv): add phy firmware handling
Merge in ICO/coreos from fix_falcon_machine_name to master
* commit 'e04b6cf215a61288f058970e4ca6031acea8f4a2':
fix(cn913x-bldn-mbv): fix machine and phy
* change the MACHINE from cn9130-bldn-mbv to cn9131-bldn-mbv
* update trusted platform to support falcon board and represnt the solidrun settings
* add patch that fixes phy issues
Now we use fw0, fw1, efi, ebg0, ebg1, rootfs0 and rootfs1 partition
name.
BREAKING CHANGE: bootX partition are now named ebgX
BREAKING CHANGE: platformX partition are now named rootfsX
sw-description files
The COREOS_SWUPDATE_EXTENDS_FOR and COREOS_IMAGE_SWUPDATE_EXTRACLASSES
variable can now be used to configure the coreos-image-swupdate to
dynamically extends some part of the sw-description by calling some
python function
This also change the beaglebone target to use a GPT
partitioned disk
BREAKING CHANGE: .swu image generated can not be used on old
device, thus the device has to be reflashed.
BREAKING CHANGE: Support for MBR formatted disk is removed, as
it was only used for Beaglebone
COREOS_EFI_SECUREBOOT_KEYDIR_HASH was intended to store a hash
of each file present in build/key in order to discard the sstate
cache on key changes. But this variables was wrongly always empty
due to a wrong check in a loop.
Merge in ICO/coreos from fix/devtool_efibootguard_script to master
* commit 'c003449178fdb31ca8f39c15516129774591944a':
fix(coreos-efibootguard.py): fix the script for older python version
* compatible node in device tree is adjusted
* config for cn9131 Falcon is removed since it is based on cn9130
* config for cn9130 based Falcon is added
commit 367814e94c introduced a change in the default
configuration of swupdate that broke our default update
system.
This commit revert this part of the emmc flasher support
for now
Merge in ICO/coreos from feat/package-group to master
* commit '5bddcaad7adf75ec63c18f72d8455204edf39cf4':
feat(coreos-container-image.bbclass): use coreos specific package-group for IMAGE_INSTALL
feat(coreos-image.bbclass): use coreos specific package-group for IMAGE_INSTALL
Merge in ICO/coreos from feat/devtool-kernel to master
* commit '1c8f7e9163ba5fec161bb858643a57274ea07882':
feat(devtool): add a generate-uki command
fix(coreos-image-uki.bbclass): use APPENDS to set the kernel arguments
refactor: use black to format python code in vscode
The generate-uki command can be used to build and sign new UKI (Unified
Kernel Image). By default all parameters are taken from bitbake but the
kernel command line and the device tree used can be customized
This introduce a new coreos-emmc-flasher-beaglebone
recipe that create a SWU file that can be used to
create the partition in the internal emmc of a beaglebone
and flash both u-boot and efibootguard.
Support for create efibootguard configuration partition
and flashing kernel and rootfs is not included.
Merge in ICO/coreos from fix/cockpit-podman-configure to master
* commit 'c1da18b58c2b4dd5727f17fb83b70e394b02fe83':
fix(cockpit-podman): don't call make clean in do_configure
Merge in ICO/coreos from fix/remove_swupdate_from_qemu to master
* commit '17855553fc0f98d2946d11eb2ecc1379a44242ec':
fix(swupdate): make swupdate dependent on EFI
Merge in ICO/coreos from feat/coreos-device to master
* commit '57107f5cea3ff2e61701c18753cacdada8d1e04f':
feat(swupdate): install swupdate-progress by default
feat(coreos-device): add a coreos-device script and a devtool plugin
The devtool plugin offer a high level integration with Bitbake and
thus is under GPLv2 license.
The coreos-device script is a low level scripts that implement all
the functionality and is not under GPLv2
Merge in ICO/coreos from chore/efibootguard-handling to master
* commit 'e02d4b95f8e257d55f70b1dfbf6435ddd564b09e':
chore(efibootguard): better handling of efibootguard related variables
Default value related to efibootguard are not set inside the distro
and MACHINE that use coreos-image and doesn't define EFI as a
MACHINE_FEATURE doesn't get the efibootguard-tools package.
We can build container with non-container machine with
coreos-container-image classes so having a MACHINEOVERRIDES
for container machines only is misleading
Merge in ICO/coreos from feat/os-release to master
* commit '60686d70f3aaca72712c82e4166923a3aa708dac':
refactor(base-files): add git information to issues files
refactor(belden-coreos): remove GIT info from DISTRO_VERSION
feat(os-release): add COREOS_GIT_BRANCH and COREOS_GIT_REVISION field
--fixed-size produce a partition of the right size but doesn't expand
the filesystem. Instead we use --size --extra-space and
--overhead-factor to have a fixed size partition and fixed size
filesystem
Merge in ICO/coreos from feat/ci-artifacts-list to master
* commit '92d900ba2f71e867d1ea672d8716bcac4fe54f35':
fix(coreos-efi-secureboot): only install sb key if needed
feat(coreos-image-ci): add a special image class to generate CI file
feat(coreos-container-image): add COREOS_IMAGE_EXTRACLASSES support
Checking for COREOS_EFI_SECUREBOOT_INSTALL_PUBKEY_IN_EFIDIR
was not done properly resulting of the key always being
installed inside the EFI partition.
Merge in ICO/coreos from refactor/images to master
* commit '0b3e395862d9dea90a9c170c3a48a12fd985e3c6':
chore(coreos-image-minimal-dev): delete the recipes
refactor: rename coreos-image-full-cmdline to coreos-image-demo
We need to generate some more file to better integrate the CI system
with this repository. The new class generate a new IMAGE.ci-artifacts
file with the list of file that need to be uploaded by the CI to our
storage server. To enable this class, the CI need to add:
`COREOS_IMAGE_EXTRACLASSES += "coreos-image-ci"`
to the auto.conf configuration file inside the build directory.
Merge in ICO/coreos from fix/swu to master
* commit 'c65869b9c9a667fb689c5d3498ef21117d5ab648':
fix(do_swuimage): use DEPENDS to get kernel arguments
fix(coreos-image): COREOS_IMAGE_EXTRACLASSES now work as expected
Merge in ICO/coreos from doc_demo_cmake_yocto to master
* commit '04547f38760b95a1fed7afef9449c4925e657fcb':
docs: removing from cmake-demo from image recipe
docs: moving cmake-demo to demo layer
docs: changing cmake version in CMakeLists.txt
docs: editing comments and removing config setting
docs: using cmake with yocto recipe - example
docs: removing from cmake-demo from image recipe
docs: moving cmake-demo to demo layer
docs: changing cmake version in CMakeLists.txt
docs: editing comments and removing config setting
docs: using cmake with yocto recipe - example
WKS_KERNEL_ARGS was using previously inside COREOS to pass the
kernel arguments between the machine configuration and image
generation. This was already replaced by the APPEND variable
that do the same and is documented in oe-core.
COREOS_IMAGE_EXTRACLASSES is used to ihnerit classes dynamically during
parsing, that mean that it can't depends on operator that operate after
parsing, like ??=, :append, ...
Now we use the ?= and += operator that operate during parsing
Merge in ICO/coreos from fix/beaglebone-bootargs to master
* commit '6b773adee07bd22c6b1047385d2b214c59dab513':
fix(beaglebone): fix kernel argument to select the right rootfs
Samuel Dolt
Patrick Vogelaar
Uli Stein
Dimitry Shapovalov
Darko Trogrlic